Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bugzilla with LDAP fails - Failing to login with AD user

88 views
Skip to first unread message

maan sing

unread,
Aug 7, 2019, 12:07:01 AM8/7/19
to
Hi,

I have been trying to integrate Bugzilla with Active directory and have below configuration set. Error: The login or password you entered is not valid.

The access log showing no error, showing 201 as status code. Any help is much appreciated.

1. LDAP is enabled.
2. LDAP configuration is set as below
LDAPserver = test-domain.com
LDAPbinddn = CN=Mansing Shinde,OU=Users,OU=test-domain,DC=test-domain,DC=com:<password>
LDAPBaseDN = OU=Users,OU=test-domain,DC=test-domain,DC=com
LDAPuidattribute = SamAccountName
LDAPmailattribute = mail

Thank you.

Thorsten Schöning

unread,
Aug 7, 2019, 3:13:55 AM8/7/19
to support-...@lists.mozilla.org
Guten Tag maan sing,
am Mittwoch, 7. August 2019 um 06:07 schrieben Sie:

> I have been trying to integrate Bugzilla with Active directory and
> have below configuration set. Error: The login or password you entered is not valid.

This means searching your LDAP was successfully in general, but either
your username wasn't found or the password is incorrect. Bugzilla
first searches LDAP for the username and then verifies the password by
binding to the LDAP using the formerly found distinguished name and
the password one has entered. Only if both of these operations
succeed, login is granted. You can simply lookup the details in the
following function:

> Bugzilla::Auth::Verify::check_credentials

So I suggest double checking your LDAPuidattribute and what you
actually input into the login form, especially things like "username"
vs. "user...@example.com" etc. The fields configured for
LDAPuidattribute should normally contain "username" only and
LDAPmailattribute should contain "user...@example.com". So depending
on how you want to login, you might use "mail" as LDAPuidattribute and
make LDAPmailattribute empty or such.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

maan sing

unread,
Aug 7, 2019, 6:09:30 AM8/7/19
to
Hi, Thanks for your response, I have tried those permutations and combinations but still no go. Where would I put Bugzilla::Auth::Verify::check_credentials and try?

Thank you.

Thorsten Schöning

unread,
Aug 7, 2019, 8:01:43 AM8/7/19
to support-...@lists.mozilla.org
Guten Tag maan sing,
am Mittwoch, 7. August 2019 um 12:09 schrieben Sie:

> Hi, Thanks for your response, I have tried those permutations and
> combinations but still no go.

That's not of much help... Instead it would be better to actually
provide how exactly your samAccountName looks like, which AD-field
stores mail addresses, what exactly you have configured for which
attempt to login, what exactly you have put into the Bugzilla login
form as username and password etc.

> Where would I put
> Bugzilla::Auth::Verify::check_credentials and try?

You put it nowhere, it's there already and you can have a look at how
things work internally. Just have a look at the following file:

> Bugzilla\Auth\Verify\LDAP.pm

mansing...@gmail.com

unread,
Aug 9, 2019, 2:37:01 AM8/9/19
to
Sorry for the delay in reply. Further to your last response, I did cross check the attributes name of Email and found the one I had in Bugzilla configuration is incorrect, so I entered the correct one and issue has been fixed, your response was really helpful so BIH THANK YOU. Great help buddy!

Thorsten Schöning

unread,
Aug 9, 2019, 4:37:14 AM8/9/19
to support-...@lists.mozilla.org
Guten Tag mansing...@gmail.com,
am Freitag, 9. August 2019 um 08:36 schrieben Sie:

> Sorry for the delay in reply. Further to your last response, I did
> cross check the attributes name of Email and found the one I had in
> Bugzilla configuration is incorrect, so I entered the correct one
> and issue has been fixed, your response was really helpful so BIH THANK YOU. Great help buddy!

Good news, but for the next time please be so kind exactly telling us
what was incorrect. Simply because others might make the same error
and currently still don't know what to look at exactly. :-)
0 new messages