Skip to content

docs: correct url path to /auth/device - #341

Closed
Jeff-Tian wants to merge 1 commit into
keycloak:mainfrom
Jeff-Tian:patch-1
Closed

Jeff-Tian wants to merge 1 commit into
keycloak:mainfrom
Jeff-Tian:patch-1

Conversation

@Jeff-Tian

Copy link
Copy Markdown

/device/auth is wrong which cause the error for example:

{
    "error": "RESTEASY003210: Could not find resource for full path: https://keycloak.jiwai.win/auth/realms/UniHeart/protocol/openid-connect/device/auth"
}

/device/auth is wrong which cause the error for example: 

```
{
    "error": "RESTEASY003210: Could not find resource for full path: https://keycloak.jiwai.win/auth/realms/UniHeart/protocol/openid-connect/device/auth"
}
```
@stianst

stianst commented Feb 16, 2023

Copy link
Copy Markdown
Contributor

These are old design documents and not documentation. We're not actively maintaining these after implementation is completed.

@stianst

stianst commented Feb 16, 2023

Copy link
Copy Markdown
Contributor

Rather than updating old and abandoned design documents we should mark these as archived, with a warning that they are likely to not include accurate information.

Another thing here is that it doesn't seem like our official documentation actually has any mention of device flow, etc. @mposolda is that correct or am I just looking in the wrong place?

@stianst stianst left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See previous comments

@stianst

stianst commented Feb 16, 2023

Copy link
Copy Markdown
Contributor

Guessing the reason why a lot of people are looking at this file is it pops up as the #1 result on a Google search for keycloak device authorization grant, and there's no mention of the proper documentation.

@tachyons

Copy link
Copy Markdown

@stianst Indeed, I wasted lot of time because of this. Does keycloak has official updated documentation regarding this?

@Jeff-Tian Jeff-Tian closed this by deleting the head repository Oct 10, 2024
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.

3 participants