RSA SecurID Access is unable to proxy to HTTPS hosts for HTTP Federation Proxy or Trusted Header Applications
Originally Published: 2018-01-29
Article Number
Applies To
RSA Product/Service Type: Identity Router
RSA Version/Condition: 1.5.4
Issue
Cause
Resolution
Workaround
On the "4. Proxy Settings" screen of your application:
- Click the Pencil icon to view the configuration of the existing Web Server you have configured.
- Make a note of the values you have configured for Proxy Hostname, Real Hostname, and any Rewrite Rules.
- Click Cancel to close the window.
- Delete the existing Web Server you added
- Click Add to add a new Web Server
- Select 'HTTP' and uncheck the checkbox that shows up labeled 'Enable HTTPS communication between user and identity router'
- Select 'HTTPS'.
- Fill in all values you had before for Proxy Hostname, Real Hostname, and any Rewrite Rules.
- Click Save
- Navigate to the "6. Portal Display" screen.
- Click Save and Finish
- Publish
Notes
Related Articles
How to add your custom logo on the login window ? 22Number of Views HTTP Federation Proxy Applications 50Number of Views Salesforce Experience Cloud - SAML Relying Party Configuration - RSA Ready Implementation Guide 17Number of Views Require a System-Generated PIN 26Number of Views CT standard attribute or external propety provider is intermittantly being exported to the HTTP header. 3Number of Views
Trending Articles
Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Governance & Lifecycle 8.0.0 Administrators Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?