Authorize fails in Portal API

Products

• CA API Developer Portal

Issue/Introduction

Users attempting to generate an access token when selecting Authorize in Portal API encounter an error when attempting to fetch the bearer token.

"Auth Error TyeError: Failed to Fetch" or browser console errors indicating ERR_CERT_AUTHORITY_INVALID.

Environment

All supported version of API Developer Portal.

Cause

This behavior is expected when a self-signed certificate is in use. Modern web browsers (e.g., Chrome) do not trust self-signed certificates as they lack a signature from a recognized Certificate Authority (CA), classifying them as a security risk. Consequently, the browser blocks the network request required to retrieve the bearer token.

Resolution

If you are working in a development or testing environment where immediate implementation of a CA-signed certificate is not feasible, you can manually force the browser to trust the self-signed certificate:

1. Open your browser's Developer Tools (F12) and navigate to the Console or Network tab to identify the exact URL triggering the ERR_CERT_AUTHORITY_INVALID error or Copy the Token_URL from Available authorizations popup window.
2. Copy the full URL and open it directly in a new browser tab.
3. The browser will display a security warning. Select Advanced and proceed to the site (e.g., "Proceed to [hostname] (unsafe)").
4. Once the browser has accepted the certificate, return to the API Portal and re-attempt the token generation process.