Custom Portal?

Customers that prefer to offer users a different look and feel from the standard RSA Via Access portal have multiple options:

1. They can embed “deep links” into existing websites.  Using this approach, an administrator can manually include the same application URLs that users access from the standard portal as links in another website.  If a user hasn’t already authenticated with the Identity Router when they click the application link, they’ll be redirected to the standard portal to log in, and then land at the requested application page.  This approach can be a quick way to include links in an existing portal, and any RSA Via Access policies will be enforced even if the user accesses the application in this way.  That said, unless the existing site has its own logic to display different content to different users, everyone will see all of the application links.
2. They can build a Custom Portal.  Using this approach, a customer can offer login, portal, and error handling pages that match the look and feel of their other websites and offer users dynamic content based on the Identity Router policies.  That is, users will only see the application links that they’re authorized to access.  Additional information about how to build a Custom Portal is available in the Custom Portal Developer’s Guide