Configure a Custom Portal Page for Web Applications

Document created by RSA Information Design and Development on Jul 14, 2016Last modified by RSA Information Design and Development on Jun 21, 2019
Version 38Show Document
  • View in full screen mode
  

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.

 

Before you begin 

 
  • You must be a Super Admin to perform this task.

  • The identity router is installed and connected to the Cloud Authentication Service.

  • If applicable, Integrated Windows Authentication (IWA) is configured as an identity provider.

  • Configure the custom portal as a trusted headers application. This configuration must point to the web server where the custom portal pages are deployed. For instructions, see Add an Application Using Trusted Headers. 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 

 
  1. In the Cloud Administration Console, click Access > Portal Settings.

  2. Click Custom. This option must be selected when you save the settings.

  3. In the Login Page field, specify the URL of the custom portal logon page.

  4. 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.   

  5. 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.

  6. Note:  HSTS blocks users from accessing application pages without a valid, trusted certificate that supports the application domain.

  7. 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.

  8. Click Save.

  9. (Optional). Click Publish Changes to activate the settings immediately.

 

 

You are here
Table of Contents > User Application Portal > Configure a Custom Portal Page for Web Applications

Attachments

    Outcomes