wpericl

Okay, looking at those now, thanks.

Thanks.
I’m using this esignature plugin, it’s bombing and sends an error to the browser. But not to the log file…

Kinda and I have some clarity on the issue now.
I installed wp 4.1 default everything.
Then I installed AD Integration and that works fine. I can log in with my domain account.
I didn’t like the fact that the site was visible at any level so I found forced login and installed that. All seemed to be well until a user said they couldn’t log in.

Here what is happening.
User logs in.
User closes browser instead of logging off.
User browses to site again and tries to log in, credentials are accepted but only the login screen appears. They cannot get past the login screen.
If user clicks on “back to Internal Wiki” can be seen here.
https://internalwiki.scinovia.com
The get the basic web page with a logout option.
If they click on log out, the next time they try they can log in fine.

So I think the problem is distilled down to the case were a user closes the browser instead of logging out.
I tried disabling AD integration plugin and used a local account. The behavior is exactly the same.

amending my post.
After some more testing. It doesn’t matter if I log out or close the browser I get looped back to the log in screen. The only way to get around it is to choose back to wiki and clicking on logout. Then I can log in. I know the password is good because if I purposely choose a bad password I get a different message saying that either the username or password is bad. I am using AD for auth with the AD Integration module. These are the only two modules that I am using.