History of Custom Authentication Tutorial
Version 3 | Current version | |
---|---|---|
For our purposes, let's assume we work for company "Foo" and we need to write a completely custom authentication piece. What follows is the super cool way to do this with ReleaseTwo and leave all exsting source pristine. Step 1: Create your custom packageAll wee need from that tutorial are steps 1 and 4 (a directory and a bit_setup_inc.php - tables are not required). Assume we make a package called foocore. Your foocore/bit_setup_inc.php should look something like:
Step 2: Create a custom class that overrides the default bitweaver user, BitPermUser. This file will be foocore/FooUser.php
Step 3: Adjust bitweaver configurationWe need to make sure foocore is scanned before the UsersPackage so add the following to your kernel/config_inc.php:$gPreScan = array( 'kernel', 'foocore', 'users', 'liberty' ); | For our purposes, let's assume we work for company "Foo" and we need to write a completely custom authentication piece. What follows is the super cool way to do this with ReleaseTwo and leave all exsting source pristine. Step 1: Create your custom packageAll we need from that tutorial are steps 1 and 4 (a directory and a bit_setup_inc.php - tables are not required). Assume we make a package called foocore. Your foocore/bit_setup_inc.php should look something like:
Step 2: Create a custom class that overrides the default bitweaver user, BitPermUser. This file will be foocore/FooUser.php
Step 3: Adjust bitweaver configurationWe need to make sure foocore is scanned before the UsersPackage so add the following to your kernel/config_inc.php:$gPreScan = array( 'kernel', 'foocore', 'users', 'liberty' ); |