Module aws_sdk_verifiedpermissions::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that Amazon Verified Permissions can respond with.
Structs§
Contains information about an action for a request for which an authorization decision is made.
An authorization request that you include in a
BatchIsAuthorizedAPI request.The decision, based on policy evaluation, from an individual authorization request in a
BatchIsAuthorizedAPI request.The configuration for an identity source that represents a connection to an Amazon Cognito user pool used as an identity provider for Verified Permissions.
The configuration for an identity source that represents a connection to an Amazon Cognito user pool used as an identity provider for Verified Permissions.
The configuration for an identity source that represents a connection to an Amazon Cognito user pool used as an identity provider for Verified Permissions.
Contains information about one of the policies that determined an authorization decision.
Contains the identifier of an entity, including its ID and type.
Contains information about an entity that can be referenced in a Cedar policy.
Contains a description of an evaluation error.
- IdentitySourceDetailsDeprecated
A structure that contains configuration of the identity source.
A structure that defines characteristics of an identity source that you can use to filter.
A structure that defines an identity source.
- IdentitySourceItemDetailsDeprecated
A structure that contains configuration of the identity source.
Contains information about a filter to refine policies returned in a query.
Contains information about a policy.
Contains information about a policy store.
Contains details about a policy template
Contains information about a resource conflict.
Contains information about a static policy.
A structure that contains details about a static policy. It includes the description and policy body.
A structure that contains details about a static policy. It includes the description and policy statement.
Contains information about a policy created by instantiating a policy template.
Contains information about a policy that was created by instantiating a policy template.
Contains information about a policy created by instantiating a policy template.
Contains configuration details of a Amazon Cognito user pool for use with an identity source.
Contains information about an update to a static policy.
Details about a field that failed policy validation.
A structure that contains Cedar policy validation settings for the policy store. The validation mode determines which validation failures that Cedar considers serious enough to block acceptance of a new or edited static policy or policy template.
Enums§
The value of an attribute.
Contains configuration information used when creating a new identity source.
Contains configuration information about an identity source.
Contains configuration information about an identity source.
Contains additional details about the context of the request. Verified Permissions evaluates this information in an authorization request as part of the
whenandunlessclauses in a policy.- When writing a match expression against
Decision, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Contains the list of entities to be considered during an authorization request. This includes all principals, resources, and actions required to successfully evaluate the request.
Contains information about a principal or resource that can be referenced in a Cedar policy.
- When writing a match expression against
OpenIdIssuer, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. A structure that contains the details for a Cedar policy definition. It includes the policy type, a description, and a policy body. This is a top level data type used to create a policy.
A structure that describes a policy definition. It must always have either an
staticor atemplateLinkedelement.A structure that describes a PolicyDefinintion. It will always have either an
StaticPolicyor aTemplateLinkedPolicyelement.- When writing a match expression against
PolicyType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. Contains a list of principal types, resource types, and actions that can be specified in policies stored in the same policy store. If the validation mode for the policy store is set to
STRICT, then policies that can't be validated by this schema are rejected by Verified Permissions and can't be stored in the policy store.Contains an updated configuration to replace the configuration in an existing identity source.
Contains information about updates to be applied to a policy.
- When writing a match expression against
ValidationMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.