Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the identification of LDAP attributes. #25

Open
steven-legg opened this issue May 20, 2024 · 0 comments
Open

Fix the identification of LDAP attributes. #25

steven-legg opened this issue May 20, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@steven-legg
Copy link

Appendix B.4 of the core specification has this to say about identifying LDAP attributes:
"Where a suitable attribute is already defined in LDAP, the XACML identifier SHALL be formed by adding the attribute name to the URI of the LDAP specification. For example, the attribute name for the userPassword defined in the RFC 2256 SHALL be:
http://www.ietf.org/rfc/rfc2256.txt#userPassword".

This is just broken. It does not produce unique identifiers and is far from complete. Definitions for many LDAP attributes can be found in more than one RFC and most LDAP attributes in use aren't defined in any RFC at all.

All attributes in LDAP are uniquely identified by an OID, e.g., userPassword is 2.5.4.35 . This should form the basis for identifying LDAP attributes in XACML. There is a URN format for OIDs, e.g., urn:oid:2.5.4.35, which should be used instead.

@steven-legg steven-legg added the bug Something isn't working label May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant