...
How the Authentication Stack Works
Startup
First the Authentication class object is constructed
This loads the configuration from the config Object. Then it runs the setup.
...
A loop is made going through each plugin in the authentication config.
Authentication Init Object is created.
it runs the apicheck function if function if this says they are compatible then it will run the init function, after this it will run the register_callback_routines function. The data from this function is then parsed onto the register_callback function
Authentication
The do_authentication function is function is called, this is the start of the authentication routine/procedure.
...
This is the first set of callbacks run and takes a Authentication a Authentication preauth object
Auth
The auth callbacks are then called with a Authentication auth object
if the returned element of the authobject is ROGO_AUTH_OBJ_SUCCESS then sets the username to be the authobject username and saves with auth plugin sucessfully authenticated.
if the returned element of the authobject is ROGO_AUTH_OBJ_LOOKUPONLY then it attempts to lookup the user using the userlookup function of the lookup stack. It then checks whats returned by this and sees if it has enough data to create a user and checks the flags from the lookup that it shouldnt create a user eg not unique user data found. If sucessfully creates user then it sets things as though it had successfully authenticated.
...
Then the postauth callbacks are called with a Authentication postauth object
After this it checks if authentication was sucessfully.
If unsuccesfull then it increases the attempt count, and creates a Authentication postauthfail object and runs the postauthfail callback
If successfull then it creates a Authentication postauthsuccess object and runs the postauthsuccess callback and then runs stores any appropriate data in the session before ending the function
...
This runs a callback after initial setup and parses the Authentication getauth object that it is parsed to it (or if not exists it creates)
...
If the display_std_form fucntion is run then it creates a Authentication displaystdform object and then includes the default login form unless the login form in config exists
...
If the display_err_form fucntion is run then it creates a Authentication displayerrform object and then includes the default errorform unless the error form in config exists
...
This is run when plugins want to determine if another plugin recognise a username, a Authentication lookupuser object is created then parsed to it.