Project

General

Profile

Actions
Copy link

Bug #6791

closed

Upgrade 2.2.6 > 2.3.2 had broken LDAP authentication

Added by m de crevoisier almost 9 years ago. Updated almost 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
User Manager / Privileges
Target version:
-
Start date:
09/16/2016
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

Hi,

I jut want to declare the following bug that we had discovered:

We upgraded one of our test firewall from version 2.2.6 to 2.3.2. Prior upgrade, we configured LDAP authentication creating a new SERVER into USER MANAGER > AUTHENTICATION SERVER. And before upgrade this was working fine, user were able to connect, edit and make changes.

Now, after upgrade, LDAP (Active Directory) users can still connect based on their Active Directory group membership. However, when you try to edit configuration and then click on SAVE, page get refreshed and change are not applied. Issue is not prsent whith local admin user.

Only solution we found was to DROP LDAP server into SERVER TAB and recreate it. This had fixed the issue.

Finally, if I go to DIAGNOSTIC > AUTHENTICATION, I'm getting the error on attached image. However, if I go to USER MANAGER > AUTHENTICATION SERVER > select a container, all my OU objects are listed. Also note that password appears in clear text on webpage....

************
Thanks guy for your assistance and for maintaining this great project
Michel de CREVOISIER
https://fr.linkedin.com/in/mdecrevoisier

Files

Capture.PNG (35.1 KB) Capture.PNG DIAGNOSTIC > AUTHENTICATION issue m de crevoisier, 09/16/2016 07:39 AM
Actions
Copy link

Also available in: Atom PDF