Handling of `state` parameter in Authentication: Update spec so clients are required to send `state` parameter
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- authentication, documentation
Research direction
Read the Authentication specification and issue #40 first, then locate the normative text governing the state parameter. Update the next-major-version wording so clients must send state while servers are not required to reject requests that omit it, and verify the requirement is stated consistently.
Written by the indexing model from the issue text.
Description
For the next major version, clients are required to send the state parameter. But servers are not required to fail a request that misses it.
See also #40.
- Dominant language
- No language data
- Stars
- 39
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from buildingSMART/foundation-API
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
buildingSMART/foundation-API#42 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
buildingSMART/foundation-API#39 · 1 comment · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
buildingSMART/foundation-API#27 · 1 comment · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
buildingSMART/foundation-API#26 · 3 comments ·
All issues in buildingSMART/foundation-API
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 94/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/differential-privacy#516 ·
-
Price: 75 USD Priority: 2 (Medium) Time: <1 Hour
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ubiquity/ai.ubq.fi#694 · 2 comments ·
Maintainers usually reply within 1 day
-
area: tooling
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
JoshuaKGoldberg/emoji-platform-data#1126 ·
Maintainers usually reply within 1 day