We want to update sentry-cli (and then all projects using it) to properly handle Org Auth Tokens.
While generally, using them works out of the box (just use them as authToken and everything should work), when we detect an org auth token we can actually use the data embedded in it.
How to detect an org auth token?
A token that starts with sntrys_ is an org auth token.
How to get embedded data?
For the purpose of sentry-cli, there are two relevant things embedded in the token:
We can get the embedded data like this: https://github.com/getsentry/sentry/blob/master/src/sentry/utils/security/orgauthtoken_token.py#L28
So basically, take the part between the _, and base64 decode it - which results in a JSON string, with org and url fields.
What to do with it?
When we detect an org auth token, we want to use the org/url set and make them optional to be configured for sentry-cli. So only the project remains necessary to configure.
We want to update sentry-cli (and then all projects using it) to properly handle Org Auth Tokens.
While generally, using them works out of the box (just use them as
authTokenand everything should work), when we detect an org auth token we can actually use the data embedded in it.How to detect an org auth token?
A token that starts with
sntrys_is an org auth token.How to get embedded data?
For the purpose of sentry-cli, there are two relevant things embedded in the token:
We can get the embedded data like this: https://github.com/getsentry/sentry/blob/master/src/sentry/utils/security/orgauthtoken_token.py#L28
So basically, take the part between the
_, and base64 decode it - which results in a JSON string, withorgandurlfields.What to do with it?
When we detect an org auth token, we want to use the org/url set and make them optional to be configured for sentry-cli. So only the project remains necessary to configure.