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

Force caseExact and uniqueness config values to be true and none when attribute type is binary #54

Merged
merged 3 commits into from
Sep 26, 2024

Conversation

sleelin
Copy link
Collaborator

@sleelin sleelin commented Sep 26, 2024

Currently, attributes of type binary can be defined with a caseExact configuration value of false, and a uniqueness configuration value of anything other than none. According to RFC7643§2.3.6, binary attributes are always case-exact and have no uniqueness.

This change ensures attributes with type binary will, by default, have caseExact and uniqueness configuration values of false and none respectively. It also adds checks to any custom configuration of binary attributes to ensure these values cannot be changed (fixes #44). Test fixtures have also been updated to reflect this change, and to more thoroughly check behaviour when invalid attribute configuration is attempted either at instantiation, or afterward.

@sleelin sleelin added the bug Something isn't working label Sep 26, 2024
@sleelin sleelin added this to the 1.2.4 milestone Sep 26, 2024
@sleelin sleelin self-assigned this Sep 26, 2024
@sleelin sleelin merged commit a82f9f2 into main Sep 26, 2024
3 checks passed
@sleelin sleelin deleted the issue/44-binary-attribute-case-exact branch September 26, 2024 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging this pull request may close these issues.

Error "Binaries have to be case-exact by definition" when connecting Keycloak (SCIM-Client) to scimmy
1 participant