Configure a Custom Portal Page for Web Applications
You can configure a custom portal page to create your own portal experience for web application users, or to integrate single sign-on (SSO) applications with an existing user portal that is already deployed within your company.
To develop custom web portal pages that enable users to authenticate to protected applications using RSA ID Plus, see Custom Web Portal Developer's Guide.
Note: Custom portal settings cannot be used in combination with standard portal settings. The Login Page, Portal Page, and Error Page settings can be used only with the custom portal.
Before you begin
You must be a Super Admin to perform this task.
The identity router is installed and connected to Cloud Access Service (CAS ).
If applicable, Integrated Windows Authentication (IWA) is configured as an identity provider.
Develop the custom web portal pages on a separate web server and configure those pages as a trusted headers application. For instructions, see Custom Web Portal Developer's Guide. You will use the configured proxy server fully qualified domain name (FQDN) from that application in the portal and error page URLs in this procedure.
Know the URLs for the logon page, custom portal page, and error handling page.
Users access the custom portal through the identity router, and the identity router proxies users to the custom portal pages.
Procedure
In the Cloud Administration Console, click Access > Portal Settings.
Click Custom. This option must be selected when you save the settings.
In the Login Page field, specify the URL of the custom portal logon page.
In the Portal Page field, specify the URL of the custom portal page that displays after a user signs in to the portal. Use the configured proxied URL (proxy server FQDN) of the portal page (https://<proxyFQDN>/portal.jsp). For example, https://portal.myco.com/portal.jsp.
In the HTTPS Strict-Transport-Security (HSTS) section, leave Enable selected to force compatible web browsers to interact with the web portal and web applications using only the HTTPS protocol. Otherwise, click Disable.
In the Error Handling Page URL field, specify the URL of the page where users are directed if a logon error occurs. Use the configured proxied URL (proxy server FQDN) of the portal page. See step 4 for examples.
Click Save.
(Optional) Click Publish Changes to activate the settings immediately.
Note: HSTS blocks users from accessing application pages without a valid, trusted certificate that supports the application domain.
Related Articles
Updating RSA SecurID Access SSL portal certificate can break Authenticate App tokencode - Authentication Manager integration Number of Views How to troubleshoot and fix most invalid proof and failed to send day data errors on the RSA Authentication Agent 7.x for … Number of Views Troubleshooting RSA SecurID Access Application Portal unsuccessful logon message due to a bad identity source bind Number of Views Users cannot authenticiate to the RSA SecurID Access Portal or protected applications using Microsoft Integrated Windows A… Number of Views Google Chrome reports NET::ERR_CERT_COMMON_NAME_INVALID due to missing Subject Alternative Names when accessing the RSA Id… Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2026-10: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities Download RSA SecurID Access Cloud User Event audit logs using Cloud Administration REST API CLU RSA SecurID Desktop Token 5.0.3 for Windows Administrator's Guide RSA SecurID Software Token 4.2.1 for Mac OS X Administrator's Guide
