put_console_authorization_configuration
async
¶
put_console_authorization_configuration(
*,
config_overrides: Optional[AsyncSigninClientConfig] = None,
target_id: Optional[TargetId] = None,
) -> PutConsoleAuthorizationConfigurationOutput
Enable console authorization configuration with automatic scope detection
Parameters:
Raises:
-
AccessDeniedException–Error thrown for access denied scenarios with flexible HTTP status mapping Runtime HTTP Status Code Mapping: - HTTP 401 (Unauthorized): TOKEN_EXPIRED, AUTHCODE_EXPIRED - HTTP 403 (Forbidden): USER_CREDENTIALS_CHANGED, INSUFFICIENT_PERMISSIONS The specific HTTP status code is determined at runtime based on the error enum value. Consumers should use the error field to determine the specific access denial reason.
-
ConflictException–Error thrown when request conflicts with current state HTTP Status Code: 409 Conflict Used when the request conflicts with the current state of the resource
-
InternalServerException–Error thrown when an internal server error occurs HTTP Status Code: 500 Internal Server Error Used for unexpected server-side errors that prevent request processing.
-
ResourceNotFoundException–Error thrown when requested resource is not found HTTP Status Code: 404 Not Found Used when the specified resource does not exist
-
TooManyRequestsError–Error thrown when rate limit is exceeded HTTP Status Code: 429 Too Many Requests Possible OAuth2ErrorCode values: - INVALID_REQUEST: Rate limiting, too many requests, abuse prevention Possible causes: - Too many token requests from the same client - Rate limiting based on client_id or IP address - Abuse prevention mechanisms triggered - Service protection against excessive token generation
-
ValidationException–Error thrown when request validation fails HTTP Status Code: 400 Bad Request Used for request validation errors such as malformed parameters, missing required fields, or invalid parameter values.
-
UnknownServiceError–The service returned an error code this client does not model.