Skip to content

FHIR-52960 - Require support for GET and POST at authorization endpoint - #30

Open
JohnMoehrke wants to merge 4 commits into
mainfrom
FHIR-52960
Open

FHIR-52960 - Require support for GET and POST at authorization endpoint#30
JohnMoehrke wants to merge 4 commits into
mainfrom
FHIR-52960

Conversation

@JohnMoehrke

Copy link
Copy Markdown
Collaborator

This change makes the IG explicit that Authorization Servers must support both GET and POST requests to the authorization endpoint for the authorization code flow, and that clients must be prepared to use either method.

FHIR-52960

@JohnMoehrke JohnMoehrke changed the title Require support for GET and POST at authorization endpoint FHIR-52960 - Require support for GET and POST at authorization endpoint Aug 7, 2026
@JohnMoehrke
JohnMoehrke marked this pull request as ready for review August 11, 2026 16:46
@JohnMoehrke
JohnMoehrke requested a review from lcmaas August 11, 2026 16:46
@lcmaas lcmaas closed this Aug 11, 2026
@lcmaas

lcmaas commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

Changes already committed to main branch; looks like we were working on this at the same time.

@JohnMoehrke

Copy link
Copy Markdown
Collaborator Author

I do not see this change applied to main.

@JohnMoehrke JohnMoehrke reopened this Aug 11, 2026
@JohnMoehrke

Copy link
Copy Markdown
Collaborator Author

I see you added POST, but you put it in a section only for authorization code flow. That is not the section the jira ticket agreed to update

@lcmaas

lcmaas commented Aug 12, 2026 via email

Copy link
Copy Markdown
Collaborator

@lcmaas

lcmaas commented Aug 12, 2026

Copy link
Copy Markdown
Collaborator

I have created a new ticket as a technical correction FHIR-58224 to fix this.

@JohnMoehrke

Copy link
Copy Markdown
Collaborator Author

to be clear... I am not at all questioning your skills and SME. I am just pointing out that the Jira ticket placed the text elsewhere... and where you placed it is limited to authorization code flow (I don't know if that is sufficient). So, I just pushed back to be clear that the change you made was not the one agreed to.

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.

2 participants