Skip to content
This repository has been archived by the owner on Apr 3, 2023. It is now read-only.

RefreshToken is loosing scopes after a page refresh #177

Open
DomSimon opened this issue Jan 11, 2022 · 0 comments
Open

RefreshToken is loosing scopes after a page refresh #177

DomSimon opened this issue Jan 11, 2022 · 0 comments

Comments

@DomSimon
Copy link

DomSimon commented Jan 11, 2022

Thank you for your gorgeous React Keycloak!

Unfortunately i may have encountered a bug.
When you login like in the fork with a specified scope (in this case phone), the scope will be reflected in the refresh token (refresh-token-1). After reloading the page the new refresh token is missing the chosen scope.(refresh-token-2).

refresh-token-1 (shortened)
{
"typ": "Refresh",
"azp": "react-test",
"scope": "openid profile email phone",
"sid": "88e83a90-6d30-406a-b4c4-18c752bf8200"
}

refresh-token-2 (shortened)

{
"typ": "Refresh",
"azp": "react-test",
"scope": "openid profile email",
"sid": "88e83a90-6d30-406a-b4c4-18c752bf8200"
}

To Reproduce
Steps to reproduce the behavior:

  1. Go to this prepared fork https://github.com/DomSimon/react-keycloak-examples
  2. When running react-router example the behavior can be seen. First state is after a login, second state is after reloading the page.

Expected behavior
Scopes remain in the refresh token.

Desktop:

  • OS: OSX
  • Browser Chrome
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant