forked from docs/doc-exports
Reviewed-by: Mützel, Andrea <andrea.muetzel@t-systems.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
6.8 KiB
6.8 KiB
Common Errors Related to IAM Authentication Information
You may encounter the following errors related to IAM authentication information:
- Incorrect IAM authentication information: AK access failed to reach the limit,forbidden
- Incorrect IAM authentication information: decrypt token fail
- Incorrect IAM authentication information: Get secretKey failed
Incorrect IAM authentication information: AK access failed to reach the limit,forbidden
{
"error_msg": "Incorrect IAM authentication information: AK access failed to reach the limit,forbidden." ......
"error_code": "APIG.0301",
"request_id": "******"
}
Possible Causes
- The AK/SK signature calculation is incorrect.
- The AK and SK do not match.
- AK/SK authentication fails for more than five consecutive times, and the AK/SK pair is locked for five minutes. (Authentication requests are rejected within this period).
- An expired token is used for token authentication.
Incorrect IAM authentication information: decrypt token fail
{
"error_msg": "Incorrect IAM authentication information: decrypt token fail",
"error_code": "APIG.0301",
"request_id": "******"
}
Possible Cause
The token cannot be parsed for IAM authentication of the API.
Solution
- Check whether the obtained token is the token of the corresponding IAM account.
- Check whether the token is correct.
- Check whether the token has been obtained in the environment where the API is called.
Incorrect IAM authentication information: Get secretKey failed
{
"error_msg": "Incorrect IAM authentication information: Get secretKey failed,ak:******,err:ak not exist",
"error_code": "APIG.0301",
"request_id": "******"
}
Possible Cause
The AK used for IAM authentication of the API does not exist.
Solution
Check whether the AK is correct.
Parent topic: API Authentication