Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.iam/v1.getProvider
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets an individual WorkloadIdentityPoolProvider.
Using getProvider
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getProvider(args: GetProviderArgs, opts?: InvokeOptions): Promise<GetProviderResult>
function getProviderOutput(args: GetProviderOutputArgs, opts?: InvokeOptions): Output<GetProviderResult>
def get_provider(location: Optional[str] = None,
project: Optional[str] = None,
provider_id: Optional[str] = None,
workload_identity_pool_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetProviderResult
def get_provider_output(location: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
provider_id: Optional[pulumi.Input[str]] = None,
workload_identity_pool_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetProviderResult]
func LookupProvider(ctx *Context, args *LookupProviderArgs, opts ...InvokeOption) (*LookupProviderResult, error)
func LookupProviderOutput(ctx *Context, args *LookupProviderOutputArgs, opts ...InvokeOption) LookupProviderResultOutput
> Note: This function is named LookupProvider
in the Go SDK.
public static class GetProvider
{
public static Task<GetProviderResult> InvokeAsync(GetProviderArgs args, InvokeOptions? opts = null)
public static Output<GetProviderResult> Invoke(GetProviderInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetProviderResult> getProvider(GetProviderArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:iam/v1:getProvider
arguments:
# arguments dictionary
The following arguments are supported:
- Location string
- Provider
Id string - Workload
Identity stringPool Id - Project string
- Location string
- Provider
Id string - Workload
Identity stringPool Id - Project string
- location String
- provider
Id String - workload
Identity StringPool Id - project String
- location string
- provider
Id string - workload
Identity stringPool Id - project string
- location str
- provider_
id str - workload_
identity_ strpool_ id - project str
- location String
- provider
Id String - workload
Identity StringPool Id - project String
getProvider Result
The following output properties are available:
- Attribute
Condition string - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- Attribute
Mapping Dictionary<string, string> - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- Aws
Pulumi.
Google Native. IAM. V1. Outputs. Aws Response - An Amazon Web Services identity provider.
- Description string
- A description for the provider. Cannot exceed 256 characters.
- Disabled bool
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- Display
Name string - A display name for the provider. Cannot exceed 32 characters.
- Expire
Time string - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- Name string
- The resource name of the provider.
- Oidc
Pulumi.
Google Native. IAM. V1. Outputs. Oidc Response - An OpenId Connect 1.0 identity provider.
- Saml
Pulumi.
Google Native. IAM. V1. Outputs. Saml Response - An SAML 2.0 identity provider.
- State string
- The state of the provider.
- Attribute
Condition string - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- Attribute
Mapping map[string]string - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- Aws
Aws
Response - An Amazon Web Services identity provider.
- Description string
- A description for the provider. Cannot exceed 256 characters.
- Disabled bool
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- Display
Name string - A display name for the provider. Cannot exceed 32 characters.
- Expire
Time string - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- Name string
- The resource name of the provider.
- Oidc
Oidc
Response - An OpenId Connect 1.0 identity provider.
- Saml
Saml
Response - An SAML 2.0 identity provider.
- State string
- The state of the provider.
- attribute
Condition String - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- attribute
Mapping Map<String,String> - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- aws
Aws
Response - An Amazon Web Services identity provider.
- description String
- A description for the provider. Cannot exceed 256 characters.
- disabled Boolean
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- display
Name String - A display name for the provider. Cannot exceed 32 characters.
- expire
Time String - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- name String
- The resource name of the provider.
- oidc
Oidc
Response - An OpenId Connect 1.0 identity provider.
- saml
Saml
Response - An SAML 2.0 identity provider.
- state String
- The state of the provider.
- attribute
Condition string - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- attribute
Mapping {[key: string]: string} - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- aws
Aws
Response - An Amazon Web Services identity provider.
- description string
- A description for the provider. Cannot exceed 256 characters.
- disabled boolean
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- display
Name string - A display name for the provider. Cannot exceed 32 characters.
- expire
Time string - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- name string
- The resource name of the provider.
- oidc
Oidc
Response - An OpenId Connect 1.0 identity provider.
- saml
Saml
Response - An SAML 2.0 identity provider.
- state string
- The state of the provider.
- attribute_
condition str - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- attribute_
mapping Mapping[str, str] - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- aws
Aws
Response - An Amazon Web Services identity provider.
- description str
- A description for the provider. Cannot exceed 256 characters.
- disabled bool
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- display_
name str - A display name for the provider. Cannot exceed 32 characters.
- expire_
time str - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- name str
- The resource name of the provider.
- oidc
Oidc
Response - An OpenId Connect 1.0 identity provider.
- saml
Saml
Response - An SAML 2.0 identity provider.
- state str
- The state of the provider.
- attribute
Condition String - A Common Expression Language expression, in plain text, to restrict what otherwise valid authentication credentials issued by the provider should not be accepted. The expression must output a boolean representing whether to allow the federation. The following keywords may be referenced in the expressions: *
assertion
: JSON representing the authentication credential issued by the provider. *google
: The Google attributes mapped from the assertion in theattribute_mappings
. *attribute
: The custom attributes mapped from the assertion in theattribute_mappings
. The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential are accepted. The following example shows how to only allow credentials with a mappedgoogle.groups
value ofadmins
:"'admins' in google.groups"
- attribute
Mapping Map<String> - Maps attributes from authentication credentials issued by an external identity provider to Google Cloud attributes, such as
subject
andsegment
. Each key must be a string specifying the Google Cloud IAM attribute to map to. The following keys are supported: *google.subject
: The principal IAM is authenticating. You can reference this value in IAM bindings. This is also the subject that appears in Cloud Logging logs. Cannot exceed 127 bytes. *google.groups
: Groups the external identity belongs to. You can grant groups access to resources using an IAMprincipalSet
binding; access applies to all members of the group. You can also provide custom attributes by specifyingattribute.{custom_attribute}
, where{custom_attribute}
is the name of the custom attribute to be mapped. You can define a maximum of 50 custom attributes. The maximum length of a mapped attribute key is 100 characters, and the key may only contain the characters [a-z0-9_]. You can reference these attributes in IAM policies to define fine-grained access for a workload to Google Cloud resources. For example: *google.subject
:principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value}
*google.groups
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value}
*attribute.{custom_attribute}
:principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value}
Each value must be a [Common Expression Language] (https://opensource.google/projects/cel) function that maps an identity provider credential to the normalized attribute specified by the corresponding map key. You can use theassertion
keyword in the expression to access a JSON representation of the authentication credential issued by the provider. The maximum length of an attribute mapping expression is 2048 characters. When evaluated, the total size of all mapped attributes must not exceed 8KB. For AWS providers, if no attribute mapping is defined, the following default mapping applies:{ "google.subject":"assertion.arn", "attribute.aws_role": "assertion.arn.contains('assumed-role')" " ? assertion.arn.extract('{account_arn}assumed-role/')" " + 'assumed-role/'" " + assertion.arn.extract('assumed-role/{role_name}/')" " : assertion.arn", }
If any custom attribute mappings are defined, they must include a mapping to thegoogle.subject
attribute. For OIDC providers, you must supply a custom mapping, which must include thegoogle.subject
attribute. For example, the following maps thesub
claim of the incoming credential to thesubject
attribute on a Google token:{"google.subject": "assertion.sub"}
- aws Property Map
- An Amazon Web Services identity provider.
- description String
- A description for the provider. Cannot exceed 256 characters.
- disabled Boolean
- Whether the provider is disabled. You cannot use a disabled provider to exchange tokens. However, existing tokens still grant access.
- display
Name String - A display name for the provider. Cannot exceed 32 characters.
- expire
Time String - Time after which the workload identity pool provider will be permanently purged and cannot be recovered.
- name String
- The resource name of the provider.
- oidc Property Map
- An OpenId Connect 1.0 identity provider.
- saml Property Map
- An SAML 2.0 identity provider.
- state String
- The state of the provider.
Supporting Types
AwsResponse
- Account
Id string - The AWS account ID.
- Account
Id string - The AWS account ID.
- account
Id String - The AWS account ID.
- account
Id string - The AWS account ID.
- account_
id str - The AWS account ID.
- account
Id String - The AWS account ID.
OidcResponse
- Allowed
Audiences List<string> - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- Issuer
Uri string - The OIDC issuer URL. Must be an HTTPS endpoint.
- Jwks
Json string - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
- Allowed
Audiences []string - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- Issuer
Uri string - The OIDC issuer URL. Must be an HTTPS endpoint.
- Jwks
Json string - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
- allowed
Audiences List<String> - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- issuer
Uri String - The OIDC issuer URL. Must be an HTTPS endpoint.
- jwks
Json String - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
- allowed
Audiences string[] - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- issuer
Uri string - The OIDC issuer URL. Must be an HTTPS endpoint.
- jwks
Json string - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
- allowed_
audiences Sequence[str] - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- issuer_
uri str - The OIDC issuer URL. Must be an HTTPS endpoint.
- jwks_
json str - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
- allowed
Audiences List<String> - Acceptable values for the
aud
field (audience) in the OIDC token. Token exchange requests are rejected if the token audience does not match one of the configured values. Each audience may be at most 256 characters. A maximum of 10 audiences may be configured. If this list is empty, the OIDC token audience must be equal to the full canonical resource name of the WorkloadIdentityPoolProvider, with or without the HTTPS prefix. For example://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/ https://iam.googleapis.com/projects//locations//workloadIdentityPools//providers/
- issuer
Uri String - The OIDC issuer URL. Must be an HTTPS endpoint.
- jwks
Json String - Optional. OIDC JWKs in JSON String format. For details on the definition of a JWK, see https://tools.ietf.org/html/rfc7517. If not set, the
jwks_uri
from the discovery document(fetched from the .well-known path of theissuer_uri
) will be used. Currently, RSA and EC asymmetric keys are supported. The JWK must use following format and include only the following fields: { "keys": [ { "kty": "RSA/EC", "alg": "", "use": "sig", "kid": "", "n": "", "e": "", "x": "", "y": "", "crv": "" } ] }
SamlResponse
- Idp
Metadata stringXml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
- Idp
Metadata stringXml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
- idp
Metadata StringXml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
- idp
Metadata stringXml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
- idp_
metadata_ strxml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
- idp
Metadata StringXml - SAML Identity provider configuration metadata xml doc. The xml document should comply with SAML 2.0 specification. The max size of the acceptable xml document will be bounded to 128k characters. The metadata xml document should satisfy the following constraints: 1) Must contain an Identity Provider Entity ID. 2) Must contain at least one non-expired signing key certificate. 3) For each signing key: a) Valid from should be no more than 7 days from now. b) Valid to should be no more than 15 years in the future. 4) Upto 3 IdP signing keys are allowed in the metadata xml. When updating the provider's metadata xml, at lease one non-expired signing key must overlap with the existing metadata. This requirement is skipped if there are no non-expired signing keys present in the existing metadata
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi