The existing identity provider to update.
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
The maximum number of hours the client can request the AWS token be valid.
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
the SPIFFE bundle endpoint profile
identity provider updated
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
The maximum number of hours the client can request the AWS token be valid.
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
Provider's identity attributes mapped to Britive service identity custom attributes.
Single identity provider attribute mapped to service identity custom attribute
How the service identity's mapped attribute value is compared against the incoming token claim. EXACT compares literally. REGEX treats the stored value as a regular expression, applied fully anchored and case-insensitively by default; a pattern may opt into case-sensitive matching with the inline (?-i) modifier.
Optional, and omitting it means EXACT. Because updating an identity provider replaces its attribute map, a client that omits this field when updating a provider resets any mapping that was REGEX back to EXACT. The stored value is then compared literally, so a pattern such as repo:myorg/myrepo:ref:refs/heads/feature/.* will no longer match any token and the identities relying on it stop authenticating. Clients that update identity providers must read the current match type and send it back, not omit it.
The amount of time in seconds, after the token has been issued/signed, Britive will attempt to validate the unverified token. Outside this window, token validation will fail.
the SPIFFE bundle endpoint profile
identity provider not found
invalid identity provider