AuthorizationServer is the Schema for the AuthorizationServers API. Manages an Authorization Server within an API Management Service.
Type
CRD
Group
apimanagement.azure.upbound.io
Version
v1beta1
apiVersion: apimanagement.azure.upbound.io/v1beta1
kind: AuthorizationServer
AuthorizationServerSpec defines the desired state of AuthorizationServer
No description provided.
Reference to a Management to populate apiManagementName.
Policies for referencing.
Selector for a Management to populate apiManagementName.
Policies for selection.
The HTTP Verbs supported by the Authorization Endpoint. Possible values are DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT and TRACE.
The mechanism by which Access Tokens are passed to the API. Possible values are authorizationHeader and query.
The Authentication Methods supported by the Token endpoint of this Authorization Server.. Possible values are Basic and Body.
Form of Authorization Grants required when requesting an Access Token. Possible values are authorizationCode, clientCredentials, implicit and resourceOwnerPassword.
Reference to a ResourceGroup in azure to populate resourceGroupName.
Policies for referencing.
Selector for a ResourceGroup in azure to populate resourceGroupName.
Policies for selection.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
The HTTP Verbs supported by the Authorization Endpoint. Possible values are DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT and TRACE.
The mechanism by which Access Tokens are passed to the API. Possible values are authorizationHeader and query.
The Authentication Methods supported by the Token endpoint of this Authorization Server.. Possible values are Basic and Body.
Form of Authorization Grants required when requesting an Access Token. Possible values are authorizationCode, clientCredentials, implicit and resourceOwnerPassword.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
AuthorizationServerStatus defines the observed state of AuthorizationServer.
No description provided.
The HTTP Verbs supported by the Authorization Endpoint. Possible values are DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT and TRACE.
The mechanism by which Access Tokens are passed to the API. Possible values are authorizationHeader and query.
The Authentication Methods supported by the Token endpoint of this Authorization Server.. Possible values are Basic and Body.
Form of Authorization Grants required when requesting an Access Token. Possible values are authorizationCode, clientCredentials, implicit and resourceOwnerPassword.
Conditions of the resource.
example
apiVersion: apimanagement.azure.upbound.io/v1beta1
kind: AuthorizationServer
metadata:
annotations:
meta.upbound.io/example-id: apimanagement/v1beta1/authorizationserver
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
apiManagementNameSelector:
matchLabels:
testing.upbound.io/example-name: example
authorizationEndpoint: https://azacctest.hashicorptest.com/client/authorize
authorizationMethods:
- GET
clientId: 42424242-4242-4242-4242-424242424242
clientRegistrationEndpoint: https://azacctest.hashicorptest.com/client/register
displayName: Test Server
grantTypes:
- implicit
resourceGroupNameSelector:
matchLabels:
testing.upbound.io/example-name: example
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.