You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After migrating the helm chart we found an issue with the base url detection. It detected the base url as http/80 instead of https/443. After changing the target port the issue was resolved.
The text was updated successfully, but these errors were encountered:
Hi @bendzsak-dpc, I've raised a ticket on our side and will look into it over our next sprint and get back to you.
Do you have some more details of the issue your are seeing? When you say base url detection, do you mean in AM configuration or it just external connectivity?
Also, did you migrate from a previous version of Helm or from Kustomize?
Thanks @lee-baines! There is an URL which gives you various AM endpoints:
FQDN/am/oauth2/realms/root/.well-known/openid-configuration
When we call this endpoint configuring http/80 as the service targetport it gives back the URL-s in http://FQDN:80 format. Then we use the 8081 port we get the URL-s https://FQDN:443 format.
The helm chart and the new customise am service is configured to forward the requests to the http (port):
https://github.com/ForgeRock/forgeops/blob/main/kustomize-ng/base/am/resources.yaml#L35
https://github.com/ForgeRock/forgeops/blob/main/charts/identity-platform/templates/am-service.yaml#L15
The old kustomize uses the 8081 port:
https://github.com/ForgeRock/forgeops/blob/main/kustomize/base/am/service.yaml#L10
After migrating the helm chart we found an issue with the base url detection. It detected the base url as http/80 instead of https/443. After changing the target port the issue was resolved.
The text was updated successfully, but these errors were encountered: