Idira Identity: How to authenticate AWS Client VPN users with Idira SAML SSO

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Workforce Identity Articles
4 min read
L4 Transporter
No ratings
This article will walk through the steps for integrating AWS Client VPN with Idira Identity for user authentication via SAML single sign-on. By enabling SAML authentication, users can use the same directory credentials for authentication, manage access based on Idira Roles or AD groups, and optionally secure VPN access with Idira MFA. 

If you already have a SAML configuration with AWS Console, you need to create a separate SAML app in Idira Identity for AWS Client VPN. You cannot reuse the SAML configuration for AWS Console for AWS Client VPN, because each uses a special ACS URL For both the VPN client and the VPN client self-service portal.

Steps

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SABl.png
 

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SACv.png

  • Set name "AWS VPN Portal Self Service", on the bottom of the first page unselect the "show in user app list" option
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG0.png
  • Click Trust
  • Click Download Metadata File from IDP section
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG1.png
  • Scroll to Service Provider Configuration and select "Manual Configuration" and make the following changes:
Save the configuration but continue with the additional configuration changes that may require some tweaking for your particular environment.
 

Permissions

Select the correct roles for AWS VPN access.
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG3.png
 

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAEq.png

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SA8A.png
 

AWS VPN Client SAML Configuration

In your Identity Admin console go to Web Apps and click the Add Web App button.
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG4.png
Click custom tab
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG5.png
Scroll and click Add for "SAML" and click Close.
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG6.png
Perform the following configuration details:
  • Set name "AWS VPN Client Authentication", on the bottom of the first page unselect the "show in user app list" option
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG7.png
  • Click Trust
  • Click Download Metadata File from IDP section
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG8.png
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAEv.png
  • Scroll to Service Provider Configuration and select "Manual Configuration" and make the following changes:
    • Set "SP Entity ID" to this exact value " urn:amazon:webservices:clientvpn"
    • Set the ACS URL to this exact url http://127.0.0.1:35001
    • Click Close on the warning
      ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAG9.png
    • Click "Both" for "Sign Response or Assertion"
    • Set NameID Format to "emailAddress"
      ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGA.png
Save the configuration but continue with the additional configuration changes that may require some tweaking for your particular environment.
 

Permissions

Select the correct roles for AWS VPN access.
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGB.png
 

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SA90.png

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAFl.png

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGC.png

Option 2: Send all Identity Roles

Click "Add" in the attribute section and perform the following configuration
  • Type "memberOf" in the Attribute Name column
  • Click the down arrow, hover on LoginUser and then pick "RoleNames"
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGD.png
 

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAFv.png

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SADv.png

var roleFilter = "AWS_";
// create empty array, or start array with default group that all users can have
var attrArray = ['default'];

// Attribute: Role
var roleNames = LoginUser.RoleNames;
for (var i=0; i < roleNames.Length; i++)
{
    if (roleNames[i].indexOf(roleFilter)>=0) {
               attrArray.push(roleNames[i]);
    }
   // else { trace(" role not used "+roleNames[i]);}
}

setAttributeArray('memberOf', attrArray);
 

AWS VPN Client Connection Setup

In your AWS Admin console go to IAM.
You will repeat these instructions for each Metadata file from Identity (you have two if you are choosing the optional Self-Service Portal).
  • Click Identity Providers on the left hand menu and click Add Provider.
  • Enter a descriptive name-eg, CyberArk_for_Portal, CyberArk_forClientAuth
  • Click Choose file and select the Metadata for the appropriate name
  • Save/Add Provider
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGE.pngka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGF.png


In your AWS Admin console navigate to the VPC dashboard.
Scroll the menu and click on Client VPN Endpoints
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGG.png
 
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SA95.png
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SA60.png
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAA0.png
You can then use these VPC security groups (as assigned via the SAML assertion) to apply different network access filtering rules to your end users.
 

ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAAv.png

  • Go to Web Apps and click "Add Web Apps"
  • Select Custom
  • Click "Add" for the Bookmark option, click Yes and click close
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGH.png
  • In the URL field paste the following partial URL: https://self-service.clientvpn.amazonaws.com/endpoints/
  • Click to your AWS VPC/VPN Endpoints administration page and copy the "Client VPN endpoint ID" to your clipboard
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGI.png
  • Return to the Idira Identity admin tab and paste the value to the end of the partial URL already pasted
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGJ.png
  • Click Description in the left/middle menu and add a good name and description
    ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGK.png
  • Click Permissions and select the same Identity Roles that are used in the AWS client VPN authentication and self-service portal SAML web apps
ka32J00000054GtQAI__eid=ka32J00000054Gt&feoid=00N2J000009R3kv&refid=0EM2J000004SAGL.png

Click Save.
 
Rate this article: