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
{{ message }}
This repository has been archived by the owner on May 3, 2024. It is now read-only.
Gandi is now advocating strongly for Personal Access Tokens and it can be a little difficult to find the correct place to get an API Key. These new Personal Access Tokens allow considerably more granularity in control, meaning we can scope them down to individual resources and specific permissions.
The primary differences between the API Key and the Personal Access Token appear to be:
Uses Authorization: Bearer <key> rather than Authorization: ApiKey <key>
Personal Access Token looks like a 40-character hex-string, whereas ApiKey is a 24 character [a-zA-Z0-9] string
This means that it could be possible to support both of these dynamically based on the shape of the supplied key and alter the Authorization: header accordingly.
Alternatively, you could store the "type" of key in the same Secret as the key itself.
The text was updated successfully, but these errors were encountered:
Gandi is now advocating strongly for Personal Access Tokens and it can be a little difficult to find the correct place to get an API Key. These new Personal Access Tokens allow considerably more granularity in control, meaning we can scope them down to individual resources and specific permissions.
The primary differences between the API Key and the Personal Access Token appear to be:
Authorization: Bearer <key>
rather thanAuthorization: ApiKey <key>
This means that it could be possible to support both of these dynamically based on the shape of the supplied key and alter the
Authorization:
header accordingly.Alternatively, you could store the "type" of key in the same Secret as the key itself.
The text was updated successfully, but these errors were encountered: