000036280 - Set up mutual authentication and HTTP header for single sign on integration with RSA Archer

Document created by RSA Customer Support Employee on Jun 15, 2018Last modified by RSA Customer Support Employee on Aug 22, 2018
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000036280
Applies ToRSA Product Set: Archer
RSA Product Version: 6.x
IssueThere are 2 main use cases for setting up mutual authentication through the use of client certificate:
  1. Added security between the user and the Archer server. In other words, the Archer would need to trust the user who is logging into Archer by making the user present a client certificate which Archer knows about
  2. For Single Sign On using HTTP header, the client can present the username in the HTTP header without presenting the password to Archer. Archer will allow the user to access the system as long as the user is defined within Archer, no password is required for further authentication. By introducing the client certificate, it allows a more secure way to access Archer.
This document describes the process of using HTTP header for passing user details to Archer, install client authentication in IIS, importing the certificate to IIS and configure Archer applications to work with client authentications.
ResolutionSee attached pdf on the setup.