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

PKCE Feature is now on for AuthServer. #625

Merged
merged 7 commits into from
Sep 18, 2024
Merged

PKCE Feature is now on for AuthServer. #625

merged 7 commits into from
Sep 18, 2024

Conversation

JoeShook
Copy link
Owner

If the ServerSettings.RequirePkce is true then it will force all UDAP Clients to register with Client.RequirePkce set to true.
But default the ServerSettings.RequirePkce is set to false. But if a client supplies the code_challenge then it will require a valid code_verifier.

JoeShook and others added 7 commits September 17, 2024 09:26
I previously mis-interpreted the TEFCA SOP for facilitated FHIR.  I thought there were new metadata items to server from Discovery but it is actually new client metadata.  The language is not explicit.  I did not unwind all the work to make Metadata extensible.  As this could be a requirement in the future.  But for now I wanted to clean this up.
If the ServerSettings.RequirePkce is true then it will force all UDAP Clients to register with Client.RequirePkce set to true.
But default the ServerSettings.RequirePkce is set to false.  But if a client supplies the code_challenge then it will require a valid code_verifier.
@JoeShook JoeShook merged commit 4898cbf into main Sep 18, 2024
3 checks passed
Udap.Common/Metadata/UdapMetaDataBuilder.cs Dismissed Show dismissed Hide dismissed
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.

1 participant