Portal API Explorer Oauth Manager Consent URL still uses port 8443

book

Article ID: 193446

calendar_today

Updated On:

Products

CA API Developer Portal

Issue/Introduction

The customer followed the steps to map the 8443 for the token manger to 443 :
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-2/customizing-the-oauth-toolkit/set-an-alternative-https-port.html

still we get an error when interactively testing the oAuth2 steps after the login with the following result on the API Explorer in Portal:



Do we need to change other configurations /perform  additional steps?
 

Environment

Release : 4.3.1

Component : API PORTAL

Resolution

There is a documentation bug which has caused this problem.

User followed the steps to map the 8443 for the token manger to 443 as outlined in the link below :
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-api-management/api-management-oauth-toolkit/4-2/customizing-the-oauth-toolkit/set-an-alternative-https-port.html

They still get an error when interactively testing the oAuth2 steps after the login with the site is not reachable using 443 port on the API Explorer in Portal.

After doing the further investigation, I found that In OTK Authorization Server Configuration, set context variable assertion should be set to host_consent_server instead of host_content_server as outlined in the above said link.

Copy the following Set Context Variable assertions:
   - host_login_server
   - host_consent_server instead of host_content_server

Attachments