Details
-
Fix
-
Status: Known Issue (View Workflow)
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Current Situation
- The LDAP configuration in shiro.ini includes a setting like this:
- {{ldapRealm.userDnTemplate = example.com
{0}
}}
- The spaces before and after \ are used for better visualization, they are not part of the configuration.
- Such a configuration allows a user to login with the samAccountName without specifying the domain, e.g. with "ap" instead of "ap@example.com" or "example.com\ap".
- {{ldapRealm.userDnTemplate = example.com
{0}
- Use of a \ in the userDnTemplate setting did work with previous releases of JOC Cockpit, e.g. 1.12.9. This does not work with release 1.13.6 of JOC Cockpit.
Desired Behavior
- Use of backslashes in a shiro.ini LDAP Configuration is supported in the same way as before.
Workaround
- Use a syntax like this:
- ldapRealm.userDnTemplate = {0}@example.com
- Should the mapping of users to roles be configured with the [users] section of shiro.ini then consider to use
- ap@example.com = , all
- instead of: example.com\ap = , all
Maintainer Notes
- This problem is introduced by newer versions of the Apache Shiro component that do not support use of a \ in Shiro configuration items.
- There is nothing that SOS can do about this, therefore, should you have used the \ syntax in releases prior to 1.13 then switch to use of the above mentioned workaround.
Attachments
Issue Links
- is related to
-
JOC-1012 Account Management should not eat backslashes in domain\account
-
- Released
-