Skip to content
This repository has been archived by the owner on Dec 13, 2022. It is now read-only.

Add a client setting to require request objects #3761

Closed
leastprivilege opened this issue Oct 23, 2019 · 4 comments
Closed

Add a client setting to require request objects #3761

leastprivilege opened this issue Oct 23, 2019 · 4 comments
Assignees
@leastprivilege
Labels
enhancement
Milestone
4.0

Comments

@leastprivilege
Copy link
Member

to enforce the usage of request object . IOW - authN on the authorize endpoint
@leastprivilege leastprivilege added this to the 3.1 milestone Oct 23, 2019
@leastprivilege leastprivilege self-assigned this Oct 23, 2019
@leastprivilege leastprivilege modified the milestones: 3.1, 4.0 Nov 28, 2019
@leastprivilege
Copy link
Member Author

Either that means all parameters must be inside - or do we need a separate setting for that?

@leastprivilege
Copy link
Member Author

also re-visit: https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-20

@stale
Copy link

stale bot commented Jan 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jan 10, 2020
@stale stale bot removed the wontfix label Jan 10, 2020
@leastprivilege leastprivilege removed this from the 4.0 milestone Jan 19, 2020
@lock
Copy link

lock bot commented Feb 18, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 18, 2020
@leastprivilege leastprivilege added this to the 4.0 milestone Feb 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@leastprivilege leastprivilege

Labels
enhancement
Projects
None yet
Milestone
4.0
Development

No branches or pull requests
1 participant
@leastprivilege