-
Previous Value Current Value Management for access tokens
RESTful api to create/delete access tokens
-
Name Previous Value Current Value Type
Bug
Improvement
-
OneDev
changed state to 'Closed' 3 years ago
Previous Value Current Value Open
Closed
-
State changed as code fixing the issue is committed (9b5e1b8b)
-
OneDev
changed state to 'Released' 3 years ago
Previous Value Current Value Closed
Released
-
State changed as build #3859 is successful
-
This api has been added to user resource.
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
Issue Votes (0)
After the upgrade I've noticed that the REST API for accessing tokens has changed (that was large upgrade), so I need to adjust REST API calls. However, changes made to access tokens (I think related to #568) resulted in the initial access token not being created. In previous version access token (when there was only one) was created during user creation. Now, when user is created ie. using REST API it is not possible to fetch user access token as no access tokens are available and there is no way to manage or create access tokens using REST API.
In my use case, user access token was used for integration with 1dev using REST API, to be able to call actions on user behalf (as user impersonation is not possible using REST API calls). Now, with the latest version, in which I cannot create access token for the user (nor obtain preexisting access token after user creation using REST API call), this is no longer possible.
I think that to solve that, it would be best to expose API to manage access tokens using REST API.
Could you please look into that and either add this new REST API or suggest me an alternative solution so this kind of integration could work?
Note: I've set affected version 8.5.0, as this is the version to which I've updated 1dev that caused this error to happen for me, but maybe lower versions are also affected as I've upgraded from version 7.9.3