- cphill
I have been toggling back & forth between endabling and disabling ASU webauth and I've run into a problem. It seems that when I disable webauth, logout, then try to login in again, the drupal core password I used to setup the user accounts doesn't work. I tried this on 2 different drupal sites. On the second one, the login worked when I had reset the core password right before disabling the mod & logging out. But when I tried a "test" login acct, the core password didn't work.
Does webauth only reference the username in the drupal core as an asurite ID in order to authenticate or does it also somehow overwrite or disable the passwords at the same time?
When I work with webauth, I generally leave it enabled at all times. I'm not a huge fan of how drupal leaves people logged in, and the implications of that + webauth. Generally, if I need to login as a non-asurite user (i.e. site user) I'll just go to siteurl/user?locallogin.
Also, for admin functions, i generally have a user setup who isn't an asurite user (i.e. username nathan) to do things, and use the locallogin. I know this didn't exactly answer your question, but maybe it helped at least :)
Yes I found this too and I had to use my backup to get out. Before disengaging the WebAuth Module, fo under Admin >> Site Configuration >> ASU WebAuth and uncheck "Force Login on User Login Page" and "Verify on every page view" first and save these changes. This will give you full access back to Durpal Authentication when you disengage the ASU Web Auth mod. Your site usernames/passwords will be untouched.