Topic on Extension talk:PluggableAuth/Archive 2

I am using PluggableAuth and SimpleSAMLphp. On Wikis upgraded from 1.35.8 to 1.39.2, this works as desired (thanks to a fix from the SimpleSAMLphp discussion page :)

If I deploy a new 1.39.2 wiki, though, I get "Fatal error authenticating user" when signing in with a SAML user. A wiki user with correct attributes is created, and if I navigate away from the error page the user is authenticated and can use the wiki as expected. I see no significant difference between the LocalSettings.php between an upgraded and a newly created wiki.

Is there any way to get more debug information from the PluggableAuth extension?

BTW: This does not only happen on the first login (i.e. when the wiki user is created), but also on subsequent logins, when the wiki user is already present.

Actually, it's MW 1.39.3, not 1.39.2 that has the problem. And the error occurs both with a newly installed 1.39.3 and one upgraded from 1.39.2. I am using the extension from https://extdist.wmflabs.org/dist/extensions/ for 1.39, which seems to be version 6.2 of PluggableAuth.

Hi man, I am facing the same problem in version 1.39.3 with PlugableAuth in 6.1 and simplesaml in 5.0.1 when I want to log in I keep getting the error 'Fatal error during user authentication. If I click on 'connect' I get my azure login page, once authenticated I come back to the mediawiki login page with the authentication error, but if I click on 'connect' again the SAML authentication is done correctly and I can navigate the wiki etc. Any idea how to solve this? Have you been able to solve it on your side or have you chosen to stay in 1.39.2 (which I understand is the latest and most up to date version with which extensions and authentication are error free?) Thank you in advance for your feedback bro' ! If the developers wanted to look into the subject it would be nice for people who use their application in a production environment !!!

Best regards,

Have you tried the latest version of PluggableAuth (6.3)? Haven't tried it myself yet, but would love to hear the results :)

I just tried MW 1.39.3 together with PluggableAuth 6.3 (68bec9b) found in https://extdist.wmflabs.org/dist/extensions/PluggableAuth-REL1_40-e6e97b1.tar.gz. Unfortunately, the error persists and I get an error on logging in.

I have the same problem after upgrading to Mediawiki 1.39.3 and extensions.

I use LDAPAuthentication2 (REL1_39-7dc2ea5) and tried multiple PluggableAuth versions (REL1_39-68bec9b, REL1_40-e6e97b1, master-ffa4ba8).

Username and password fields are not displayed at all.

Update: LDAPAuthentication2 master-dd5b9e3 fixed my problem.

I am getting this exact error but it comes on subsequent log ins within the same browser session. I can log in and out using AzureAD, but when I try to log in again within the same browser session I get this error.

Even after getting the error, clicking home page then log in again only to find out the user is authenticated. This extra step is confusing for users.

MW Version 1.39.2

Running extensions PluggableAuth v6.2 and SimpleSaml v5.0.

The SimpleSaml framework installed is 2.0.

Hi,

MW 1.39.3

SimpleSAMLphp library 2.0.3  

PluggableAuth 6.2

SimpleSAMLphp extension 5.0.1

same issue i am also facing , actually Ad authenticates me but after authenticattion its sending me to https://wiki.com/index.php/Special:PluggableAuthLogin displaying.

Fatal error authenticating user.

But when i click on login button or main page , iam authenticated/login & my username is displaying properly.

app is working properly, not getting why saml redirecting me to Special:PluggableAuthLogin

if i could redirect directly to main_page then error is not there.

Need to know where we can set redirect_url or relaystate , so that i can redirect to main_page directly.

Please suggest!!

@Pooja2425 @Gachangi @AVNeu @Joernc unibi see my comment here: https://www.mediawiki.org/w/index.php?title=Topic:Xhudwz0uk7mftwiw&topic_showPostId=xjmbn0ggffctfom5#flow-post-xjmbn0ggffctfom5

Basically, updating PluggableAuth and SimpleSAMLphp both to the new version 7.0-dev resolves this issue for me. Seems like it was a known bug that was fixed recently: https://phabricator.wikimedia.org/T322828