Closed jdcano-bpe closed 3 years ago
Hello @michaelstingl
Thanks for your answer. Yes, I followed that diagram and all is working fine and I can get an Access Token without any problem.
What I would like to know is if it is possible to not have to authorize an Application / ClientID that has been Authorized in a previous request. And if it is not possible, then it does not have much more sense to have in the personal space of the user an OAUTH2 section saying that a specific Application has been authorized (like in the first image attached) if you have to authorize it again every time you want to get a new Access Token.
Thanks a lot again.
I still don't get what you mean with "authorize it again"? Click the [Authorize]
button again? This should only happen once.
it does not have much more sense to have in the personal space of the user an OAUTH2 section saying that a specific Application has been authorized (like in the first image attached)
Independent from your issue, I also think this has limited value to display for the user.
I still don't get what you mean with "authorize it again"? Click the
[Authorize]
button again? This should only happen once.
That is not happening only once for me.
In my case, I have to authorize every time I make a request, even if I can get a Code and Access Token in a previous request. I tried with multiple Applications (existing one and adding a new one) but it always ask me to Authorize again.
Thanks again.
As long as the refresh token is used to obtain a new access token this screen will not be used. But as soon as a fresh access token + refreshtoken pair is requested this page will pop up again. (for implicit flow where no refresh token exists - if wil popup everytime the access token expires)
while this can be anoying this is the only way to allow a user after logout to switch the user. it is an implementation limitation of the current solution
it is advised to use a full features open id connect provider and the owncloud open id connect app.
Hello everyone,
I was trying to check in the documentation about this topic, but I dont know if it is the right behavior or not, that is why I creating this issue.
So far, all is working fine with the OAUTH2 application, I can make and go through the full OAUTH2 flow but I have to Authorize all the time the same ClientID, which I dont know if is the right behavior. I think once a ClientID have been authorized to be used, it should not ask again for it.
Steps to reproduce
Expected behaviour
Once a ClientID is authorized, I should NOT have to authorize it again
Actual behaviour
Every time a want to generate a new Access Token, I have to Authorize the same ClientID even if it is authorized in order to get the CODE to get the Access Token
Server configuration
No errors have been found.
The config report: config_report_20210122.txt
List of activated apps:
Are you using encryption: NO
Are you using an external user-backend, if yes which one: NO.
Client configuration
NOT USING CLIENT
Logs
Thanks a lot in advance.