Closed Bug 729744 Opened 12 years ago Closed 12 years ago

LDAP Auth With Internal Web App Failing

Categories

(Infrastructure & Operations Graveyard :: NetOps: DC ACL Request, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jeads, Assigned: jabba)

Details

We're actively using/developing a python/django web application for internal use in Mozilla that uses LDAP.  It looks like LDAP authentication started failing today and we have not changed the application.  These are some of the main LDAP settings from a bash script that the web application has been using:

export SISYPHUS_LDAP_SERVER_URI=ldap://pm-ns.mozilla.org
export SISYPHUS_LDAP_BIND_DN=uid=binduser,ou=logins,dc=mozilla
export SISYPHUS_LDAP_BIND_PASSWORD=*********** 
export SISYPHUS_LDAP_RESTRICTED_GROUP=cn=security_group_posix,ou=groups,dc=mozilla 

The production host is located on Mozilla-MPT and is called http://qp-bughunter/bughunter at 10.8.73.244

Are there new LDAP settings that the application should be using? I commented out the PASSWORD field but please let me know if that needs to be changed also.
Thanks
Jeads
Yes, the binduser account is deprecated. I'll create you a new one.
Assignee: network-operations → jdow
I've created a new bind user for you to use for this application. I've placed the credentials in:

10.8.73.244:/home/mozauto/ldap-bind-credentials

(this is the only access I have to this server)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Great! Thanks for the speedy fix, it works.
Status: RESOLVED → UNCONFIRMED
Ever confirmed: false
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.