https://bugzilla.wikimedia.org/show_bug.cgi?id=52649

       Web browser: ---
            Bug ID: 52649
           Summary: After upgrade MediaWiki and LdapAuthentication -
                    Failed to authenticate
           Product: MediaWiki extensions
           Version: REL1_21 branch
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Unprioritized
         Component: LdapAuthentication
          Assignee: [email protected]
          Reporter: [email protected]
    Classification: Unclassified
   Mobile Platform: ---

Created attachment 13074
  --> https://bugzilla.wikimedia.org/attachment.cgi?id=13074&action=edit
LdapAuthentication Schema Extension for Postgres

We have just upgraded MediaWiki from v1.16.2 to v1.21.1, and also upgraded
extension LdapAuthentication (v2.0c-18-g013532d).

Here we post our problem and the solution we implemented. We would like to a 
confirmation if this is a valid solution and/or if some additional procedure is
needed.

Thank you!

Problem: Authentication fails because of LdapAuthentication extension missing
schema update.
We tried to run several times php maintenance/update.php, but problem is not
solved. 

Solution: After some reading, we found that schema update for
LdapAuthentication is not working. So we did this manually, using as reference
extensions/LdapAuthentication/ldap.sql file. We changed this file for our
postgres setup. We attached to this ticket the file we used.

The command issued to update schema:
psql -U mwuser mediawikidb -f ldap-v5.sql

Now everything looks fine.

More information on our setup:
  Product            Version
  MediaWiki          1.21.1
  PHP                5.3.3-7+squeeze1
  PostgreSQL         9.1.7-1
  LdapAuthentication 2.0c-18-g013532d

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to