Loading...
 
Skip to main content

LDAP / Active directory

Forum List Topic List

Forums » LDAP / Active directory » PAM authentication -- first login attempt fails, but second works
 
Thread actions
Print this page
  • Print all pages

    • PAM authentication -- first login attempt fails, but second works

    Posted by Scott Norwood United States

    This not specifically an LDAP question, but I want to use Tiki Wiki with PAM authentication. I have configured this and ensured that the users in question have login access to the server where Tiki is running.

    When a new user logs into Tiki for the first time, the login attempt will fail, presumably because the user has no Tiki account at that time. After this, the Tiki account is created and subsequent logins to Tiki will succeed.

    Is this the normal and expected behavior? Tiki is getting the login and password information through PAM without difficulty, so that seems to be configured properly.

    This is not a deal-breaker, but is still pretty annoying behavior. Thoughts?

    Thanks.

    Reads: 1445
    Posted by Scott Norwood United States
    Additional information: the initial login failure generates an "Authentication error." The second attempt will succeed.
    Posted by Torsten Fabricius Germany

    Hello @Scott Norwood ,

    sadly I have no useful information for you. Anyway I want to say hello, as I think maybe not too many Tiki admins use PAM. I would find it sad, if you got no answer in the forums.

    The behaviour you describe is pretty annoying indeed and I am wondering, if a SAML configuration of Tiki might have the same behaviour!?

    Scott Norwood wrote:
    Additional information: the initial login failure generates an "Authentication error." The second attempt will succeed.


    Your added information might be helpful for the devs. Maybe you want to ask for help in the developers mailing-list ( tikiwiki-devel at lists.sourceforge.net ), as this might be more a coding problem or you want to file a bug report, if you agree to consider this behaviour a (minor) bug ( https://dev.tiki.org/File-a-bug ).

    Regards,
    Torsten