Map of all the roles currentUser has across all the teams she is a part of
default
4
teamIdToRegionId
map<string, string>
The following two maps indicate the API host to contact for
customers with non-US deployments. Every team is located on one
region, and the maps specify which region each of the teams you can
access are located, and for each of them what the relevant
hostnames are.
Send up a PEM encoded certificate signing request for mothership to sign
You can then use this certificate later on prove your authenticity
to other people.
Mothership will override any parameters it sees fit (will use same public key)
So always use the LoginResult#userCertificate you get back down
optional
2
proxiedUserEmail
string
Login as this user, but with a proxy super admin account
If the account is not a super admin, the login would be rejected
The returned token and user will be the proxied user's, with the `proxyUserEmail`
set to the admin's email
Validates a token gotten by a third party service and returns a Parsable auth token.
Provider: which provider is used for authenticate.
Token: the token to validate with the provider.
Options: Provider specific
This endpoint checks if the user is on multiple teams. If they are it returns a list of teams to select from
or if the user is only on a single team they will be logged in
* Parses a Parsable IDP Authorization header Bearer token. If the user belongs to multiple teams this returns a list of teams to select from.
* If the user is only on a single team they will be logged in.