is_authorized_with_token async ¶

async def is_authorized_with_token(
    self,
    policy_store_id: "capo_verifiedpermissions.types.policy_store_id.PolicyStoreId",
    *,
    config_overrides: Optional[AsyncVerifiedPermissionsClientConfig] = None,
    identity_token: Optional["capo_verifiedpermissions.types.token.Token"] = None,
    access_token: Optional["capo_verifiedpermissions.types.token.Token"] = None,
    action: Optional[
        "capo_verifiedpermissions.types.action_identifier.ActionIdentifier"
    ] = None,
    resource: Optional[
        "capo_verifiedpermissions.types.entity_identifier.EntityIdentifier"
    ] = None,
    context: Optional[
        "capo_verifiedpermissions.types.context_definition.ContextDefinition"
    ] = None,
    entities: Optional[
        "capo_verifiedpermissions.types.entities_definition.EntitiesDefinition"
    ] = None,
) -> "capo_verifiedpermissions.types.is_authorized_with_token_output.IsAuthorizedWithTokenOutput":
    """<p>Makes an authorization decision about a service request described in the parameters. The principal in this request comes from an external identity source in the form of an identity token formatted as a <a href="https://wikipedia.org/wiki/JSON_Web_Token">JSON web token (JWT)</a>. The information in the parameters can also define additional context that Verified Permissions can include in the evaluation. The request is evaluated against all matching policies in the specified policy store. The result of the decision is either <code>Allow</code> or <code>Deny</code>, along with a list of the policies that resulted in the decision.</p> <p>Verified Permissions validates each token that is specified in a request by checking its expiration date and its signature.</p> <important> <p>Tokens from an identity source user continue to be usable until they expire. Token revocation and resource deletion have no effect on the validity of a token in your policy store</p> </important>

            Args:
                policy_store_id: <p>Specifies the ID of the policy store. Policies in this policy store will be used to make an authorization decision for the input.</p> <p>To specify a policy store, use its ID or alias name. When using an alias name, prefix it with <code>policy-store-alias/</code>. For example:</p> <ul> <li> <p>ID: <code>PSEXAMPLEabcdefg111111</code> </p> </li> <li> <p>Alias name: <code>policy-store-alias/example-policy-store</code> </p> </li> </ul> <p>To view aliases, use <a href="https://docs.aws.amazon.com/verifiedpermissions/latest/apireference/API_ListPolicyStoreAliases.html">ListPolicyStoreAliases</a>.</p>
                identity_token: <p>Specifies an identity token for the principal to be authorized. This token is provided to you by the identity provider (IdP) associated with the specified identity source. You must specify either an <code>accessToken</code>, an <code>identityToken</code>, or both.</p> <p>Must be an ID token. Verified Permissions returns an error if the <code>token_use</code> claim in the submitted token isn't <code>id</code>.</p>
                access_token: <p>Specifies an access token for the principal to be authorized. This token is provided to you by the identity provider (IdP) associated with the specified identity source. You must specify either an <code>accessToken</code>, an <code>identityToken</code>, or both.</p> <p>Must be an access token. Verified Permissions returns an error if the <code>token_use</code> claim in the submitted token isn't <code>access</code>.</p>
                action: <p>Specifies the requested action to be authorized. Is the specified principal authorized to perform this action on the specified resource.</p>
                resource: <p>Specifies the resource for which the authorization decision is made. For example, is the principal allowed to perform the action on the resource?</p>
                context: <p>Specifies additional context that can be used to make more granular authorization decisions.</p>
                entities: <p>(Optional) Specifies the list of resources and their associated attributes that Verified Permissions can examine when evaluating the policies. These additional entities and their attributes can be referenced and checked by conditional elements in the policies in the specified policy store.</p> <important> <p>You can't include principals in this parameter, only resource and action entities. This parameter can't include any entities of a type that matches the user or group entity types that you defined in your identity source.</p> <ul> <li> <p>The <code>IsAuthorizedWithToken</code> operation takes principal attributes from <b> <i>only</i> </b> the <code>identityToken</code> or <code>accessToken</code> passed to the operation.</p> </li> <li> <p>For action entities, you can include only their <code>Identifier</code> and <code>EntityType</code>. </p> </li> </ul> </important>

            Raises:
                capo_verifiedpermissions.errors.access_denied_exception.AccessDeniedException: <p>You don't have sufficient access to perform this action.</p>
                capo_verifiedpermissions.errors.internal_server_exception.InternalServerException: <p>The request failed because of an internal error. Try your request again later</p>
                capo_verifiedpermissions.errors.throttling_exception.ThrottlingException: <p>The request failed because it exceeded a throttling quota.</p>
                capo_verifiedpermissions.errors.validation_exception.ValidationException: <p>The request failed because one or more input parameters don't satisfy their constraint requirements. The output is provided as a list of fields and a reason for each field that isn't valid.</p> <p>The possible reasons include the following:</p> <ul> <li> <p> <b>UnrecognizedEntityType</b> </p> <p>The policy includes an entity type that isn't found in the schema.</p> </li> <li> <p> <b>UnrecognizedActionId</b> </p> <p>The policy includes an action id that isn't found in the schema.</p> </li> <li> <p> <b>InvalidActionApplication</b> </p> <p>The policy includes an action that, according to the schema, doesn't support the specified principal and resource.</p> </li> <li> <p> <b>UnexpectedType</b> </p> <p>The policy included an operand that isn't a valid type for the specified operation.</p> </li> <li> <p> <b>IncompatibleTypes</b> </p> <p>The types of elements included in a <code>set</code>, or the types of expressions used in an <code>if...then...else</code> clause aren't compatible in this context.</p> </li> <li> <p> <b>MissingAttribute</b> </p> <p>The policy attempts to access a record or entity attribute that isn't specified in the schema. Test for the existence of the attribute first before attempting to access its value. For more information, see the <a href="https://docs.cedarpolicy.com/policies/syntax-operators.html#has-presence-of-attribute-test">has (presence of attribute test) operator</a> in the <i>Cedar Policy Language Guide</i>.</p> </li> <li> <p> <b>UnsafeOptionalAttributeAccess</b> </p> <p>The policy attempts to access a record or entity attribute that is optional and isn't guaranteed to be present. Test for the existence of the attribute first before attempting to access its value. For more information, see the <a href="https://docs.cedarpolicy.com/policies/syntax-operators.html#has-presence-of-attribute-test">has (presence of attribute test) operator</a> in the <i>Cedar Policy Language Guide</i>.</p> </li> <li> <p> <b>ImpossiblePolicy</b> </p> <p>Cedar has determined that a policy condition always evaluates to false. If the policy is always false, it can never apply to any query, and so it can never affect an authorization decision.</p> </li> <li> <p> <b>WrongNumberArguments</b> </p> <p>The policy references an extension type with the wrong number of arguments.</p> </li> <li> <p> <b>FunctionArgumentValidationError</b> </p> <p>Cedar couldn't parse the argument passed to an extension type. For example, a string that is to be parsed as an IPv4 address can contain only digits and the period character.</p> </li> </ul>
                capo_verifiedpermissions.errors.resource_not_found_exception.ResourceNotFoundException: <p>The request failed because it references a resource that doesn't exist.</p>
                capo_verifiedpermissions.errors.UnknownServiceError: The service returned an error code this client does not model.

            Examples:
                IsAuthorizedWithToken - Example 1
                The following example requests an authorization decision for a user who was authenticated by Amazon Cognito. The request uses the identity token provided by Amazon Cognito instead of the access token. In this example, the specified information store is configured to return principals as entities of type CognitoUser. The policy store contains a policy with the following statement.

    permit(
        principal == CognitoUser::"us-east-1_1a2b3c4d5|a1b2c3d4e5f6g7h8i9j0kalbmc",
        action,
        resource == Photo::"VacationPhoto94.jpg"
    );

                >>> await client.is_authorized_with_token(policy_store_id='C7v5xMplfFH3i3e4Jrzb1a', action={'actionId': 'View', 'actionType': 'Action'}, resource={'entityId': 'vacationPhoto94.jpg', 'entityType': 'Photo'}, identity_token='EgZjxMPlbWUyBggAEEUYOdIBCDM3NDlqMGo3qAIAsAIA')
    """

    async def _handler(
        req: "AsyncOperationRequest[capo_verifiedpermissions.types.is_authorized_with_token_input.IsAuthorizedWithTokenInput]",
    ) -> AsyncOperationResponse[
        "capo_verifiedpermissions.types.is_authorized_with_token_output.IsAuthorizedWithTokenOutput"
    ]:
        import capo_verifiedpermissions._operations.verified_permissions.is_authorized_with_token

        (
            output,
            http_response,
        ) = await capo_verifiedpermissions._operations.verified_permissions.is_authorized_with_token.async_is_authorized_with_token(
            req.options, req.input
        )
        return AsyncOperationResponse(output=output, response=http_response)

    def _redact_input(
        input_: "capo_verifiedpermissions.types.is_authorized_with_token_input.IsAuthorizedWithTokenInput",
    ) -> dict[str, Any]:
        import capo_verifiedpermissions.types.is_authorized_with_token_input

        return capo_verifiedpermissions.types.is_authorized_with_token_input.redact_sensitive(
            input_
        )

    def _redact_output(
        output: "capo_verifiedpermissions.types.is_authorized_with_token_output.IsAuthorizedWithTokenOutput",
    ) -> dict[str, Any]:
        import capo_verifiedpermissions.types.is_authorized_with_token_output

        return capo_verifiedpermissions.types.is_authorized_with_token_output.redact_sensitive(
            output
        )

    interceptors_, options_ = self.operation_options(
        config_overrides,
        OperationLogging(
            "IsAuthorizedWithToken",
            redact_input=_redact_input,
            redact_output=_redact_output,
        ),
    )
    input_: capo_verifiedpermissions.types.is_authorized_with_token_input.IsAuthorizedWithTokenInput = {
        "policy_store_id": policy_store_id
    }
    if identity_token is not None:
        input_["identity_token"] = identity_token
    if access_token is not None:
        input_["access_token"] = access_token
    if action is not None:
        input_["action"] = action
    if resource is not None:
        input_["resource"] = resource
    if context is not None:
        input_["context"] = context
    if entities is not None:
        input_["entities"] = entities

    response = await aexecute_pipeline(
        AsyncOperationRequest(input=input_, options=options_),
        handler=_handler,
        interceptors=list(interceptors_),
    )
    await response.response.aclose()
    return response.output