class
Amazonite::Iam::CreateOpenIDConnectProviderRequest
- Amazonite::Iam::CreateOpenIDConnectProviderRequest
- Reference
- Object
Defined in:
iam/create_open_id_connect_provider_request.crConstructors
- .from_xml(node : XML::Node) : self
- .new(url : String, client_id_list : Array(String) | Nil = nil, thumbprint_list : Array(String) | Nil = nil, tags : Array(Tag) | Nil = nil)
Instance Method Summary
-
#==(other : self)
Returns
trueif this reference is the same as other. -
#client_id_list : Array(String) | Nil
Provides a list of client IDs, also known as audiences.
-
#client_id_list=(client_id_list : Array(String) | Nil)
Provides a list of client IDs, also known as audiences.
-
#hash(hasher)
See
Object#hash(hasher) -
#tags : Array(Tag) | Nil
A list of tags that you want to attach to the new IAM OpenID Connect (OIDC) provider.
-
#tags=(tags : Array(Tag) | Nil)
A list of tags that you want to attach to the new IAM OpenID Connect (OIDC) provider.
-
#thumbprint_list : Array(String) | Nil
A list of server certificate thumbprints for the OpenID Connect (OIDC) identity provider's server certificates.
-
#thumbprint_list=(thumbprint_list : Array(String) | Nil)
A list of server certificate thumbprints for the OpenID Connect (OIDC) identity provider's server certificates.
- #to_query_params(prefix : String) : Array(Tuple(String, String))
-
#url : String
The URL of the identity provider.
-
#url=(url : String)
The URL of the identity provider.
- #validate! : Nil
Constructor Detail
Instance Method Detail
Returns true if this reference is the same as other. Invokes same?.
Provides a list of client IDs, also known as audiences. When a mobile or web app registers with
an OpenID Connect provider, they establish a value that identifies the application. This is the
value that's sent as the client_id parameter on OAuth requests.
You can register multiple client IDs with the same provider. For example, you might have multiple applications that use the same OIDC provider. You cannot register more than 100 client IDs with a single IAM OIDC provider.
There is no defined format for a client ID. The CreateOpenIDConnectProviderRequest operation
accepts client IDs up to 255 characters long.
Provides a list of client IDs, also known as audiences. When a mobile or web app registers with
an OpenID Connect provider, they establish a value that identifies the application. This is the
value that's sent as the client_id parameter on OAuth requests.
You can register multiple client IDs with the same provider. For example, you might have multiple applications that use the same OIDC provider. You cannot register more than 100 client IDs with a single IAM OIDC provider.
There is no defined format for a client ID. The CreateOpenIDConnectProviderRequest operation
accepts client IDs up to 255 characters long.
A list of tags that you want to attach to the new IAM OpenID Connect (OIDC) provider. Each tag consists of a key name and an associated value. For more information about tagging, see Tagging IAM resources in the IAM User Guide.
If any one of the tags is invalid or if you exceed the allowed maximum number of tags, then the entire request fails and the resource is not created.
A list of tags that you want to attach to the new IAM OpenID Connect (OIDC) provider. Each tag consists of a key name and an associated value. For more information about tagging, see Tagging IAM resources in the IAM User Guide.
If any one of the tags is invalid or if you exceed the allowed maximum number of tags, then the entire request fails and the resource is not created.
A list of server certificate thumbprints for the OpenID Connect (OIDC) identity provider's server certificates. Typically this list includes only one entry. However, IAM lets you have up to five thumbprints for an OIDC provider. This lets you maintain multiple thumbprints if the identity provider is rotating certificates.
This parameter is optional. If it is not included, IAM will retrieve and use the top intermediate certificate authority (CA) thumbprint of the OpenID Connect identity provider server certificate.
The server certificate thumbprint is the hex-encoded SHA-1 hash value of the X.509 certificate used by the domain where the OpenID Connect provider makes its keys available. It is always a 40-character string.
For example, assume that the OIDC provider is server.example.com and the provider stores its
keys at https://keys.server.example.com/openid-connect. In that case, the thumbprint string
would be the hex-encoded SHA-1 hash value of the certificate used by
https://keys.server.example.com.
For more information about obtaining the OIDC provider thumbprint, see Obtaining the thumbprint for an OpenID Connect provider in the IAM user Guide.
If your OIDC provider's discovery endpoint and JWKS endpoint (jwks_uri) use different
certificates or hosts, include the thumbprints for both endpoints in this list.
A list of server certificate thumbprints for the OpenID Connect (OIDC) identity provider's server certificates. Typically this list includes only one entry. However, IAM lets you have up to five thumbprints for an OIDC provider. This lets you maintain multiple thumbprints if the identity provider is rotating certificates.
This parameter is optional. If it is not included, IAM will retrieve and use the top intermediate certificate authority (CA) thumbprint of the OpenID Connect identity provider server certificate.
The server certificate thumbprint is the hex-encoded SHA-1 hash value of the X.509 certificate used by the domain where the OpenID Connect provider makes its keys available. It is always a 40-character string.
For example, assume that the OIDC provider is server.example.com and the provider stores its
keys at https://keys.server.example.com/openid-connect. In that case, the thumbprint string
would be the hex-encoded SHA-1 hash value of the certificate used by
https://keys.server.example.com.
For more information about obtaining the OIDC provider thumbprint, see Obtaining the thumbprint for an OpenID Connect provider in the IAM user Guide.
If your OIDC provider's discovery endpoint and JWKS endpoint (jwks_uri) use different
certificates or hosts, include the thumbprints for both endpoints in this list.
The URL of the identity provider. The URL must begin with https:// and should correspond to
the iss claim in the provider's OpenID Connect ID tokens. Per the OIDC standard, path
components are allowed but query parameters are not. Typically the URL consists of only a
hostname, like https://server.example.org or https://example.com. The URL should not contain
a port number.
You cannot register the same provider multiple times in a single Amazon Web Services account. If you try to submit a URL that has already been used for an OpenID Connect provider in the Amazon Web Services account, you will get an error.
The URL of the identity provider. The URL must begin with https:// and should correspond to
the iss claim in the provider's OpenID Connect ID tokens. Per the OIDC standard, path
components are allowed but query parameters are not. Typically the URL consists of only a
hostname, like https://server.example.org or https://example.com. The URL should not contain
a port number.
You cannot register the same provider multiple times in a single Amazon Web Services account. If you try to submit a URL that has already been used for an OpenID Connect provider in the Amazon Web Services account, you will get an error.