-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TokenStorage not working correctly #8
Comments
Hi, what happens when you authenticate for the second time? Does the token get created? |
Hello! Same here. |
Trying to explain a bit more without a code sample. I'm using scopes ['api', 'openid', 'profile']. For me the getToken method sets scopeKey to 'api__openid__profile'. The insertToken method, scopeKey is set to 'openid profile api'. The tokens map is set to: |
I saw that I've had wrong order in my scope list. The scopes that returned token contains is [openid profile api]. A different order than my configuration. But even if a change my configuration to exactly that order to: ['openid', 'profile', 'api'] it still doesn't work. On this line scopeKey is openid__profile__api. But the tokens key is : Hope that explains it a bit more. |
Hi @jimad7 and @ResoDev, thank you for taking the time of looking into the issue! I'm already working on these issues, fixes should be released very soon. |
Just published version 1.2.3... Does it solve your issues? |
It does for me. Thank you! |
Hi, it does for me too. Thank you! |
Fine! |
Hi
I've a problem with TokenStorage. I'm using OAuth2Helper.AUTHORIZATION_CODE with scope parameters ['api', 'openid', 'profile']. After login i'm trying to do a get. But the token is null from TokenStorage and i'm prompt to login again. There seems to be a problem with the scopeKey not being correctly defined when writing and getting tokens from TokenStorage.
The text was updated successfully, but these errors were encountered: