gcloud beta iam workforce-pools providers update-oidc

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 the attribute_mappings. google.profile_photo and google.display_name are not supported.
• attribute: The custom attributes mapped from the assertion in the attribute_mappings.

The maximum length of the attribute condition expression is 4096 characters. If unspecified, all valid authentication credential will be accepted.

Example: Only allow credentials with a mapped google.groups value of admins.

"'admins' in google.groups"

Each key must be a string specifying the Google Cloud IAM attribute to be produced.

The following predefined keys are currently supported:

• google.subject: required field that indicates the principal that is being authenticated to IAM, and will be logged in all API accesses for which Cloud Audit Logging is configured.

• google.groups: optional field that indicates asserted groups that the user should be considered to belong to. You can create IAM bindings using the groups attribute and access to a resource will be granted if any of the groups asserted here match a group in the respective binding.

• google.display_name: optional field that overrides the name of the user. If not set, google.subject will be displayed instead. This attribute cannot be used in IAM policies. The maximum length of this field is 100 characters.

• google.profile_photo: optional fields that may be set to a valid URL specifying the user's thumbnail photo. When set, the image will be visible as the user's profile picture. If not set, a generic user icon will be displayed instead. This attribute cannot be used in IAM policies.

Custom attributes can also be mapped by specifying attribute.{custom_attribute}, replacing {custom_attribute} with the name of the custom attribute to be mapped. A maximum of 50 custom attribute mappings can be defined. The maximum length of a mapped attribute key is 2048 characters and may only contain the characters [a-z0-9].

These attributes can then be referenced in IAM policies to define fine-grained access for the workforce pool to Google Cloud resources by specifying:

• google.subject: principal://iam.googleapis.com/locations/global/workforcePools/{pool}/subject/{value}

{"google.subject": "assertion.sub"}

{
  "keys": [
     {
          "kty": "RSA/EC",
          "alg": "<algorithm>",
          "use": "sig",
          "kid": "<key-id>",
          "n": "",
          "e": "",
          "x": "",
          "y": "",
          "crv": ""
     }
  ]
}
```. Use a full or relative path to a local file containing the value of jwk_json_path.

*--web-sso-additional-scopes*=[_WEB_SSO_ADDITIONAL_SCOPES_,…]::

Additional scopes to request for the OIDC authentication on
top of scopes requested by default. By default, the `openid`, `profile`
and `email` scopes that are supported by the identity provider are
requested.

Each additional scope may be at most 256
characters. A maximum of 10 additional scopes may be configured.

*--web-sso-assertion-claims-behavior*=_WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR_::

The behavior for how OIDC Claims are included in the `assertion` object used for attribute mapping and attribute condition.
Use `merge-user-info-over-id-token-claims` to merge the UserInfo Endpoint Claims with ID Token
Claims, preferring UserInfo Claim Values for the same Claim Name. Currently this option is only
available for Authorization Code flow.
Use `only-id-token-claims` to include only ID token claims. _WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR_ must be one of: *assertion-claims-behavior-unspecified*, *merge-user-info-over-id-token-claims*, *only-id-token-claims*.

*--web-sso-response-type*=_WEB_SSO_RESPONSE_TYPE_::

Response Type to request for in the OIDC Authorization Request for web sign-in.
Use `code` to select the authorization code flow
Use `id-token` to select the implicit flow. _WEB_SSO_RESPONSE_TYPE_ must be one of: *code*, *id-token*, *response-type-unspecified*.

:: At most one of these can be specified:


*--clear-client-secret*:::

Clear the OIDC client secret.

*--client-secret-value*=_CLIENT_SECRET_VALUE_:::

The OIDC client secret. Required to enable Authorization Code flow for web sign-in.

:: At most one of these can be specified:


*--clear-extra-attributes-config*:::

Clear the extra attributes configuration.

*--extra-attributes-client-id*=_EXTRA_ATTRIBUTES_CLIENT_ID_:::

The OAuth 2.0 client ID for retrieving extra attributes from the identity provider. Required to get the Access Token using client credentials grant flow.

*--extra-attributes-client-secret-value*=_EXTRA_ATTRIBUTES_CLIENT_SECRET_VALUE_:::

The OAuth 2.0 client secret for retrieving extra attributes from the identity provider. Required to get the Access Token using client credentials grant flow.

*--extra-attributes-filter*=_EXTRA_ATTRIBUTES_FILTER_:::

The filter used to request specific records from IdP. In case of attributes type as AZURE_AD_GROUPS_MAIL, it represents the filter used to request specific groups for users from IdP. By default all the groups associated with the user are fetched. The groups that are used should be mail enabled and security enabled. See https://learn.microsoft.com/en-us/graph/search-query-parameter for more details.

*--extra-attributes-issuer-uri*=_EXTRA_ATTRIBUTES_ISSUER_URI_:::

OIDC identity provider's issuer URI. Must be a valid URI using the 'https' scheme. Required to get the OIDC discovery document.

*--extra-attributes-type*=_EXTRA_ATTRIBUTES_TYPE_:::

Represents the identity provider and type of claims that should be fetched. _EXTRA_ATTRIBUTES_TYPE_ must be (only one value is supported): *azure-ad-groups-mail*.