You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Public API has so far only been proxying requests to server. As a result, the authentication on Public API only checks for the presence of credentials, rather than actually authenticate the credentials.
In order to guard access to the Tokens endpoints, we need to be able to authenticate the call. Currently, the resource guards are buried in server without any ability for us to access them from the Public API. To give us access, we're gonna add a method to server which checks if the user (as determined by the connection credentials) is allowed to perform the required operation against tokens.
Extend server with APIs to check if the current user is able to perform an action on personal access tokens
Actions are - get, create, delete, list, regenerate
This new API needs to be added to gitpod-service.go to be invokable from public API
The text was updated successfully, but these errors were encountered:
Thinking about this more, I believe we can simplify this by using the following: getLoggedInUser. This will resolve to the current identity and will allow us to ensure that requested data matches the user.
Public API has so far only been proxying requests to server. As a result, the authentication on Public API only checks for the presence of credentials, rather than actually authenticate the credentials.
In order to guard access to the Tokens endpoints, we need to be able to authenticate the call. Currently, the resource guards are buried in server without any ability for us to access them from the Public API. To give us access, we're gonna add a method to server which checks if the user (as determined by the connection credentials) is allowed to perform the required operation against tokens.
The text was updated successfully, but these errors were encountered: