fix(GitLab Node): Update credential test endpoint #5166
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Github issue / Community forum post (link here to close automatically):
https://community.n8n.io/t/no-access-via-accesstoken-to-self-hosted-gitlab-ce-ee/21802
To sum it up:
The credentials check of the GitLab node is doing wrong, because it's checking the
/users
endpoint. But that endpoint is used for listing all users of an instance and requires theapi
scope. So if the token has no scope forapi
the credentials test will fail.A better approach to checking the credentials, without needing any special scope for it, is the endpoint
/personal_access_tokens/self
(see https://docs.gitlab.com/ee/api/personal_access_tokens.html#using-a-request-header) which shows everything related to the currently used accessToken (e.g. the scopes and expiration date).