• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 160
  • Last Modified:

Solution to Implement PIV Card Authentication via Juniper PULSE MAG 4610 Appliance

I have read several articles on implementing the PIV (Personal Identity Cards  or CAC (common access card) Authentication via a webpage Portal similar to when you visit www.af.mil.  I have not as of this moment found anything definitive in the capability and/or configuration of this appliance to be able to integrate this technology to replace RSA into Active Directory, any help would be much appreciated.
  • 3
1 Solution
btanExec ConsultantCommented:
Not much info but mainly has to do with user certificate (stored also in the PIV) authentication via Pulse Secure client - from the "Machine and User Authentication Through a Pulse Connection for Pulse Policy Secure"
Pulse Secure client supports certificate authentication for establishing Layer 2 and Layer 3 connections. On Windows endpoints, a Pulse client connection accesses client certificates located in the Local Computer personal certificate store to provide machine authentication, or user certificates located in a user’s personal certificate store or on a smart card for user authentication. A Pulse connection can access certificates from only one location.
You can create a Pulse connection that uses System Local, Active Directory, or RSA ACE
server authentication to verify the user and a certificate to verify machine identity before
establishing a connection. To do so, you must first enable an option for the Pulse connection
that allows the connection to check the client certificates located in the Local Computer
personal certificate store.
The following list summarizes the steps to configure a Pulse connection on a Windows endpoint
that authenticates both the user and the machine. For detailed procedures on how to perform
each configuration task, see the related documentation links.
 Install a machine authentication certificate in the Local Computer personal certificate store of
the Windows endpoint and configure the Pulse server certificate server.
 Create a Pulse connection for the target Pulse server. The connection type can be UAC
(802.1X) or Connect Secure or Policy Secure (L3). The Connection is established option is
typically set to Manually by the user or Automatically at user login.
 In the User Connection Preferences section of the connection properties, click the check box
labeled Select client certificate from machine certificate store. This option enables the Pulse
connection to perform the machine authentication as part of the Pulse connection attempt.
 Create a sign-in policy on the Pulse server that specifies a user realm. The realm
authentication server can be a System Local, Active Directory, or RSA ACE server.
 Configure a certificate restriction on the realm to enable the Pulse server to request a client
certificate. Be sure to enable the option labeled Only allow users with a client-side certificate
signed by Trusted Client CAs to sign in. Because the Pulse connection is configured to use
the machine certificate, the user authentication takes place by means of the realm certificate
cgooden01Author Commented:
Solution used for implementation.  Thank you.
btanExec ConsultantCommented:
Thanks for sharing - any other further queries?
btanExec ConsultantCommented:
Solution is used as per shared.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now