Posted by biohabit on July 6, 2006 at 9:56pm
Jump to:
| Project: | Webserver authentication |
| Version: | master |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Currently you can't use the webserver_auth module with loginToboggan unless you hack the module and comment out these two lines ....
#menu_set_active_item('user');
#$return = menu_execute_active_handler();
and change the drupal_set_message to....
drupal_set_message(t('Login - It appears you are not logged in and the page you are trying to reach has restricted access.
You will have to retype the URL you were trying to, after logging in.
'), 'error');
which still doesn't completely work because it doesn't direct the users back to the URL they where trying to get to.
Comments
#1
try disabling the 'Present login form on access denied (403):' feature--the code you mentioned runs as part of that.
#2
Thanks, but that is not the effect I'm looking for. I'm wanting people to be able to put in a URL (i.e. from bookmark or from an e-mail) for something with restricted content and have a process for checking to see if they are logged in and if not re-direct them to a login screen. Then once they are logged in, the are re-directed again, back to the URL they where trying to get to. I was under the impression that LoginToboggan would do this, but it doesn't seem to be working with the webserver_auth module.
#3
afaict, webserver_auth isn't meant to be used with standard user logins, but instead supplants them with webserver authentication for drupal sites. in fact, the module suggests completely disabling the user login block:
i think what you really want is for the webserver_auth module to respect the original destination upon successful login using it's schema. moving this to a feature request for the right module.
#4