Hi There,
I recently installed PlatformUI in our environment. In the standalone setup, where IG, AM, and IDM are on a single server, the Platform UI installation and configuration were straightforward. However, in a more complex environment where IG, AM, and IDM are on separate servers with load balancing, I encountered some challenges.
In the standalone server setup, I used the server hostname in the AM IDM URLs, as shown below:
export AM_URL=https://servername:8443/difam
export AM_ADMIN_URL=https://servername:8443/difam/ui-admin
export IDM_REST_URL=https://servername:9443/openidm
export IDM_ADMIN_URL=https://servername:9443/admin
export IDM_UPLOAD_URL=https://servername:9443/upload
export IDM_EXPORT_URL=https://servername:9443/export
export ENDUSER_UI_URL=https://servername:8443/enduser
export PLATFORM_ADMIN_URL=https://servername:8443/platform
Now, in an environment with multiple instances of AM/IDM servers and a load balancer on top, I am unsure which URL to use in the export command (Load balancer URL, Individual server URL, or IG URL).
Could someone please provide guidance on how to address this situation?
Env diagram for your reference
Hello @kannan.kandan,
Thank you for reaching out to the Community site. I apologize for the long delay in the response. Please review the ForgeRock documentation link below on adapting the Platform UI configuration for IG. Here the IG URL is used to direct traffic through IG.
https://backstage.forgerock.com/docs/platform/7.4/sample-setup/protect-deployment.html#protect-configure-ig
In the example provided:
Replace the /path/to/platform_env content with settings that direct traffic through IG:
AM_URL=https://platform.example.com:9443/am
AM_ADMIN_URL=https://platform.example.com:9443/am/ui-admin
IDM_REST_URL=https://platform.example.com:9443/openidm
IDM_ADMIN_URL=https://platform.example.com:9443/admin
IDM_UPLOAD_URL=https://platform.example.com:9443/upload
IDM_EXPORT_URL=https://platform.example.com:9443/export
ENDUSER_UI_URL=https://platform.example.com:9443/enduser-ui
PLATFORM_ADMIN_URL=https://platform.example.com:9443/platform-ui/
ENDUSER_CLIENT_ID=end-user-ui
ADMIN_CLIENT_ID=idm-admin-ui
THEME=default
PLATFORM_UI_LOCALE=en
I hope this helps!
Warm Regards,
Ed
Hi Edward,
Thank you for responding; your input is highly valued. The issue at hand pertains to the fact that we have three DNS names for IG, not just a single one. The rationale behind having multiple DNS names is linked to the realm configuration, with two distinct realms—realmA and realmB. The DNS name for realmA is example.com, while for realmB, is test.net and example.com.au. However, the challenge lies in the limitation of PlatformUI, which only supports a single URL in the configuration.
Apologies for the delayed response. I just came across this and wanted to share some additional information that might be helpful, along with the relevant documentation that Ed provided: ForgeRock Platform 7.4 Deployment Guide.
If you have IG configured to front AM in a Platform UI setup,
You can remove the DNS alias for your AM realms, allowing you to set the Base URL Source setting for all AM realms to point to a singular IG. This should help everything work as expected.
Alternatively, you can continue using the DNS alias for your AM realms, but you’ll need to configure each realm’s Base URL source setting to match its specific DNS alias. Additionally, you’ll need to set up your IG to handle all the different domain names so that requests and responses for each AM realm work as expected.
I hope you find this helpful!
1 Like
