Skip to main content

Troubleshooting

This document is a guide for resolving IAM-related issues.

CORS error when requesting API authentication token​

When a client application attempts to obtain an API authentication token, the following error may occur:

CORS error message
Access to XMLHttpRequest at 'https://iam.kakaocloud.com/identity/v3/auth/tokens' from origin 'http://61.109.239.46' has been blocked by CORS policy: 
Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.

This CORS error occurs because KakaoCloud's IAM API does not allow cross-origin requests for security reasons.
When your application sends a request to the IAM API endpoint, the origin differs from the IAM server, which results in a CORS error.

▶️ Resolution: To bypass the error, configure a proxy server that receives the client request and forwards it to the IAM server to retrieve the token response.

API authentication token shows 3-hour validity​

The token appears to have a 3-hour expiration because the issued_at and expired_at fields are in UTC time.

▶️ Resolution: Add +9 hours to both issued_at and expired_at to view the time in KST (Korea Standard Time). The token is actually valid for 12 hours.

Timeout error when obtaining API authentication token​

Timeout errors when requesting an API token from a specific server may occur if the server's IP is blocked due to repeated token requests from a loop in the code.

▶️ Resolution: Follow these steps to identify and resolve the issue:

  1. Launch another server using the same IP and check whether both servers can obtain a token.

  2. If neither can obtain a token, resolve the issue using one of the following methods:

    • Operate the service from a server with a different IP address.
    • Contact KakaoCloud Support to request unblocking of the server's IP.

"Invalid token" popup appears​

After logging in to the console, an "Invalid token" popup may appear when multiple login sessions are active in a single browser.

▶️ Resolution: Ensure only one IAM login session is active in the browser to prevent this issue.