Actions
Bug #14127
open
Captive Portal - LDAP server with special characters in description fails to authenticate in
Status:
New
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
All
Description
When you have an LDAP configured that has commas (and likely other special characters) two things fail:
1) Selection from the configuration page does not re-select later on edit (but writes to config)
2) Users authenticating via CP fail to succeed.
System tests through PF allow authentication to pass so this appears to be isolated to CP.
User reported this from a 1537 but the comma-related issue is likely platform agnostic.
Tested on 23.01
No data to display
Actions