Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The custom proxy-path is not working properly #2162

Closed
cbabey opened this issue Sep 11, 2023 · 0 comments · Fixed by wso2/product-apim#13269
Closed

The custom proxy-path is not working properly #2162

cbabey opened this issue Sep 11, 2023 · 0 comments · Fixed by wso2/product-apim#13269

Comments

@cbabey
Copy link

cbabey commented Sep 11, 2023

Description

The following two errors were encountered when configuring the custom proxy path for the APIM server URLs as guided in the documentation[1].

  1. The login page of all the portals(publisher/dev portal/admin) would hang without any response. Upon investigation, it was discovered that the logincontext URI was returning a 404 error due to the incorrect API context being added to the URL (apim..).

GET https://api.am.wso2.com/apim../logincontext?sessionDataKey=42b12bdd-5213-4778-8d93-d7c4f445f226&application=apim_publisher&tenantDomain=carbon.super&_=1693976490656 404 (Not Found)

image

  1. Resource forbidden (403) error response was returned when accessing the carbon management console.

image

[1]https://apim.docs.wso2.com/en/latest/install-and-setup/setup/setting-up-proxy-server-and-the-load-balancer/adding-a-custom-proxy-path/

Steps to Reproduce

  1. Configure the APIM and ingress as guided in the documentation[1]
  2. Acess the publisher portal and carbon console using the proxy context

[1]https://apim.docs.wso2.com/en/latest/install-and-setup/setup/setting-up-proxy-server-and-the-load-balancer/adding-a-custom-proxy-path/

Affected Component

APIM

Version

4.2.0

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant