flyingmongoose
Forum Replies Created
-
Forum: Plugins
In reply to: [Authorizer] Chain existing WP users to external services usersWhat a pity we didn’t start troubleshooting at this point !
Looking to the apache log searching for PHP errors revealed the issue pretty fast.I have installed Bbpress, when users were already existing.
Bbpress somehow “knows” about these users but they are not configured, to use the forum.Authorizer finds the users, says they are O.K. but then they somehow seem to get redirected to the bbpress login and not to the wp-login.
Bbpress-login fails as the users have no configured role there.That’s at least, what I read from the logs.
So it’s not Authorizer but a rare combination of plugins, which lead to this strange behaviour.
I think we can close this, as the log gave me an idea, how to resolve the issue.Best regards and thank you very much for you kind help !
flyingmongoose
Forum: Plugins
In reply to: [Authorizer] Chain existing WP users to external services usersYes I checked this.
user_login and user_nicename do match.
The only difference I found: user_login starts with an uppercase character.There are no unicode characters included.
Forum: Plugins
In reply to: [Authorizer] Chain existing WP users to external services usersHere is, what happens, when new WP users get created by authorizer:
The username is “user” (all lowercase)
Email is “[email protected]”
First and last name display correctly
Logon with this new user works flawlessAn already existing user, which is not created by Authorizer but has the same informations as above will not be able to log in, with “user” only, in the username field.
Forum: Plugins
In reply to: [Authorizer] Chain existing WP users to external services usersHello @pkarjala !
Yes, I’m using the LDAP settings for AD communication.
In previous postings I saw uppercase letters in AD attributes might cause issues.
Thus I set them to lowercase from the beginning on.Email Adresses also lowercase ever since.
A “special” with our domain login account:
The login account is “[email protected]”
The mail account is “[email protected]”
But I don’t think, this is really special at all, as it is recommended, to not use the external domain for internal AD structures.E-Mail adresses do match perfectly.
Tested this with my own one, and with another user.
I can log on when I enter “[email protected]” in the username field.
I cannot log on, when I enter “user” without the local domain part of the username.
Then I get kicked somewhere to limbo and end up with a blank browser page without anny error displays