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

Allow JSON as a valid claim_value_type #260

Merged
merged 1 commit into from
Mar 24, 2020

Conversation

dwaynebailey
Copy link
Contributor

Fixes #255

I'm not sure if tests need expansion for this, couldn't find one testing the valid types.

@dwaynebailey dwaynebailey force-pushed the json_claim_value branch 2 times, most recently from 332ae1b to 14f608f Compare March 24, 2020 11:16
Copy link
Owner

@mrparkers mrparkers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for the PR!

@mrparkers mrparkers merged commit 1389a9f into mrparkers:master Mar 24, 2020
@dwaynebailey dwaynebailey deleted the json_claim_value branch March 31, 2020 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

resource_keycloak_openid_user_attribute_protocol_mapper::claim_value_type should allow JSON
2 participants