KB40514 - How to configure certificate authentication with Pulse Desktop Client for Linux
KB44881 - How to configure SSL Decryption on Virtual Server
KB24522 - How to restrict user certificate authentication to Active Directory users only
KB44770 - How to configure vWAF to send logs to a syslog server
KB43813 - Certificate authentication fails with error "Missing or Invalid Certificate" or other applications that rely on certificate authentication may fail after upgrading to the Pulse Mobile 7.0.0 for iOS
KB22227 - How to configure the Syslog server
KB41008 - How to configure the Smart Card Authentication
KB44686 - How to configure Azure Multi Factor Authentication for RADIUS
KB44421 - 'Missing or invalid client certificate' error with certificate authentication after upgrading to Pulse Connect Secure 9.1R4 or above.
KB21321 - How to configure Pulse Connect Secure (PCS) for IKEv2 and MSCHAPv2 authentication in Windows 7
What would you like to know?
< Back to search results
KB18267 - How to configure Certificate Authentication to backend servers
Last Modified Date
8/3/2015 11:38 AM
This article provides information on how to configure Certificate Authentication to backend servers.
Problem or Goal
In PCS 7.0 and later, there is a feature which enables customers to enforce client authentication on their secure backend servers.
This allows the PCS gateway to present an admin-configured certificate to these servers for authentication.
Several customers need backend servers to require strict access control, including the use of client certificates for SSL establishment.
This feature allows the PCS gateway to present a certificate to such a backend server; so as to conform to these SSL policies.
The PCS gateway can be easily configured to present a client certificate to one or more secure backend servers.
This feature enables customers to mandate strict SSL policies on their backend servers by configuring client authentication.
To configure a certificate to be presented to a 2-way SSL protected resource, perform the following procedure:
To upload a Client Auth Certificate, go to
System > Configuration > Certificates > Client Auth Certificates
To create a Client Authentication Resource Policy, go to
Users > Resource Policies > Web > Client Authentication
An auto-policy in a resource profile can also be created; go to
Users > Resource profiles > Web > Auto-policy [Client Authentication]
Was this article helpful?
Please tell us how we can make this article more useful.