Skip to content

OAuth Flow: Query Params vs. JSON Body #137

Description

@pawel-kow

7.3.6. OAuth Flow: Apply Template to Domain.

Considering the async flow must use POST, is there an advantage to allow either
query parameters or JSON post body? Do service providers need to support a
combination of query parameters and JSON body? If there are duplicates, which
takes priority? Can the name/value pairs be split between body and query? If
groupId exists in both, are the values combined?

I think the body variant is not actually needed or used, but I would have to check. This is a good catch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    IETFIssues reported from IETF processIETF Draft: AsyncPrioIssues with priority to talk about

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions