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
RSA SecurID: Identity Sources configurations "You have reached the limit of ldap resources you can add please remove a re… Number of Views Checking name resolution and port connectivity for Web Tier instance on a supported Red Hat platform - RSA Authentication … Number of Views Cannot log into the Security Console. Error is 'authentication error' and 'session expired' and 'please try again' in RSA … Number of Views RSA Authentication Agent for Web 7.1.2 on Microsoft IIS and Windows 2008 Server R2 has http 500 error when protecting ADFS… Number of Views How to Forward RSA Authentication Manager 8.4 or Later Logs to Multiple Syslog Servers Using rsyslog Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Governance & Lifecycle 8.0.0 Installation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA MFA Agent for UNIX Platform Support Matrix Performing RADIUS authentication tests with NTRadPing to RSA Authentication Manager
