Community
Participate
Working Groups
Every time I log into tuleap using openId, I get prompted for the authorization and I would not expect this since I've already authorized Tuleap to get access to the necessary information. Here is the message I see: This application will be able to: Know who you are on accounts.eclipse.org.
Hi Pascal, is it possible the issue is on tuleap side of things? You should get a refresh token with your access token and that should allow tuleap to fetch a new access token once the original is expired. This should remove the need to redirect the user to accounts.eclipse.org to authorize tuleap?
Hi Chris, I'm not familiar with the implementation so I've cc'ed Manuel to insights from the Tuleap dev team.
I CC'd the developer who dealt with implementation Tuleap side for more details
Hello, It is not possible for Tuleap to use a refresh token to get a new access token. When the user is redirected to accounts.eclipse.org it means that Tuleap does not know who the user is and without knowing which user try to authenticate it is not possible to select the corresponding refresh token. To me, it seems that the OAuth2 server used by Eclipse does not remember which rights has been granted to an application. At least as a user I not able to find the administration panel allowing me to revoke the permissions granted to an app in my user's settings.
(In reply to Thomas Gerbet from comment #4) > Hello, > > It is not possible for Tuleap to use a refresh token to get a new access > token. When the user is redirected to accounts.eclipse.org it means that > Tuleap does not know who the user is and without knowing which user try to > authenticate it is not possible to select the corresponding refresh token. > > To me, it seems that the OAuth2 server used by Eclipse does not remember > which rights has been granted to an application. At least as a user I not > able to find the administration panel allowing me to revoke the permissions > granted to an app in my user's settings. You are correct because the session for the user is expired on tuleap. I did a quick search in the issue queue for the oauth2_server drupal module and it looks like this feature was requested but never completed: https://www.drupal.org/node/2460805
*** Bug 520643 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This issue has been migrated to https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/278.
