In general the PKI code doesn't seem to decode the values it receives from the DS. In most cases it's not a problem, but there might be cases where it will produce incorrect results.
For example the UGSubsystem.buildGroup() doesn't decode the value of the UID attribute obtained from the DN in the group's uniqueMember attribute. This is probably fine because a UID usually doesn't contain characters that needs escaping. However, there could be other codes that use attributes that have higher likelihood to contain escaped characters (e.g. cn).
In the UGSubsystem.buildGroup() the code simply gets everything between the first equal sign and comma. For example:
uid=testuser,ou=People,dc=example,dc=com ==> testuser
Ideally all escaped characters (e.g. \2b), quoted values (e.g. "John Smith"), or hex values (e.g #a24f) should be decoded into the proper characters. The current code does not do that.
uid=test\2buser,ou=People,dc=example,dc=com ==> test\2buser
Metadata Update from @edewata: - Issue assigned to vakwetu - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/912
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)