OAI / OAI/sig-security

OAuth refreshUrl property

Open
#21 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
6
Forks
3
Avg merge
1h 54m
Merged PRs (30d)
1

Description

Hi,

Is there any reason why the non-standard refreshUrl property was added to OAI?

Obtaining a new Access Token using the Refresh Token should be done using the TokenEndpoint, as stated in RFC 6749 (OAuth 2.0 Authorization framework):

"3.2. Token Endpoint
The token endpoint is used by the client to obtain an access token by presenting its authorization grant or refresh token. The token endpoint is used with every authorization grant except for the implicit grant type (since an access token is issued directly)."

Thanks,

Philippe

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the issue's cited RFC 6749 token-endpoint requirement and locate where the refreshUrl property is defined. The payload names no files or tests, so first identify the relevant definition and any related specification context. Done requires a maintainer decision on whether the non-standard property should be retained or changed.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.