EUCbackup Default chapterWorkspace ONE Access as Third-Party IDP in ADFS

Workspace ONE Access as Third-Party IDP in ADFS

This lab will guide you through how to leverage Workspace ONE Access as a claims provider in ADFS. The added value a customer will get for doing such an integration is to leverage the authentication methods that Workspace ONE Access has to offer such as mobile single-sign-on.

In this scenario we will assume the customer has already federated the desired application with ADFS. For the sake of this lab socialcast will be used as the application (Relying Party) in ADFS.

First you will configure Workspace ONE Access in ADFS as the claims provider by importing the idp metadata. We will then set which claims we would like to send Workspace ONE Access for authentication.

Lastly you will set up ADFS as  the application source in Workspace ONE Access.

ADFS Configuration

  1. On your controlcenter2 open FireFox and browse to your unique Workspace ONE Access Admin tenant.
  2. Select the System Domain from the drop down domain drop down option and authenticate using the administrator account
  3. In the admin console click on catalog and click Settings
  4. In the Left Navigation column select SAML metadata under SaaS Apps
  5. Right click the Identity Provider (IdP) metadata and select save link as ... IDP.xml
  6. In the browser window that opens navigate to the Software folder on the desktop and open the ADFS folder and select Save
  1. Open the Remote Desktop folder on the desktop and RDP to the ADFS server
  2. Select and right click the Start button and select run. Type services.msc
  3. Browse down and right click Active Directory Federation Services and select Properties
    1. Now select the Log On tab at the top and select Browse. Now on the pop-up click locations and select the domain and type ADFSsvc and select Check Names. This should automatically find the the user that we are looking for. Select OK.
    2. Now type in the password twice VMware1! and hit OK now right click the service and click Start. This should now start the service,

go back

  1. In Server Manager and at the top, select Tools and select  AD FS Management
  2. When the AD FS Management interface is open navigate to Claims Provider Trusts (Only Active Directory should be present)
  3. Right Click Claims Provider Trust and select Add Claims Provider Trust...
  4. Click Start on the first Welcome page
  5. Then select Import data about the claims provider from a file
  6. Select Browse and navigate to Desktop > Software > ADFS and select the idp.xml and click Open
  7. Click next on the page and write Workspace ONE Access Livefire in the Display name click Next >  Next > Close. Now you will see Active Director and Workspace ONE Access Livefire as Claims Providers
  8. Right Workspace ONE Access Livefire and select Edit Claim Rules...
  1. Now Select Add Rule...
  2. From the next page select from the drop down "Send Claim Using a Custom Rule" select Next
  3. Type Windows Accountname Claim for the claim rule name
  4. Paste the below into the custom rule field:
c:[Type == "", Properties[""] == "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified"] => issue(Type = "", Issuer = "AD AUTHORITY", OriginalIssuer = c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType);

5. Select Finish and OK

Configure Workspace ONE Access

  1. Return to the ControlCenter2 and open Firefox
  2. Using your browser go to you unique Workspace ONE Access tenat
  3. Login with System Domain using user:administrator password:VMware1!
  4. Now click on Catalog and select Settings
  5. Navigate to Application Sources under the Saas Apps on the left hand side and select ADFS to configure the App Source.


  1. Open the firefox  browser on a new Tab and  Browse to
  2. Select Save File and go to the Downloads folder. (Chrome will download the file automatically)
  3. Open the File using Notepad++ and copy the contents of the XML by pressing ctrl + a then ctrl + c
  4. Then go back to the ADFS Application Source configuration on Workspace ONE Access and select next.
  5. Paste the contents of the FederationMetadata.xml into the URL/XML field.  Click NEXT
  6. Click Next in the Access Policies and SAVE on the Summary Page


  1. Now head back into the ADFS settings by selecting ADFS in the Application Source page.
  2. Navigate to Configuration on the left hand side and  change Username Format to Unspecified
  3. Enter the following value under Username Value
    • NB! there are no spaces in the below syntax

4. Click on advanced Properties and set Signature Algorithm to SHA256 with RSA and Digest Algorithm to SHA256

5. Select NEXT at the bottom of the page

6. Click SAVE on the Summary page

SAML Test Application (Socialcast)

Now that we have integrated Workspace ONE Access as a claims provider to ADFS we can now test an application that has been federated with ADFS. Socialcast has been  pre-configured under the Relying Party trust as an application in  ADFS. Configuring the SAML application is not part of this lab.

  1. Navigate to
  2. Select as Employee on the look up account page  
  3. Notice now you will be redirected to ADFS Home Realm Discovery Screen (HRD)
  4. You will then have two options for authentication (The claims providers configured in ADFS)
    1. Workspace ONE Access LiveFire
    2. Active Directory
  5. Now Select Workspace ONE Access LiveFire, You will then be redirected to authentication to Workspace ONE Access
  6. Select Next with the domain selected
  7. Type your custom user account and VMware1! and sign in
  8. Follow the wizard for first time users. example below


Adding ADFS app to Workspace ONE Access

In certain scenarios admins might want to provide access to the Relying party configured in ADFS directly in the Workspace ONE catalog. This is made possible via the ADFS integration. We are essentially using a redirect to the Relying Party. Let's add the socialcast application to the catalog.

  1. Log into you unique Workspace ONE Access Admin console using the local directory
  2. Now navigate to Catalog then select NEW and give it the name: Socialcast
  3. Click on Select File below Icon and select the socialcast.jpg file in the Download folder and select open. click NEXT
  4. In the Configuration page select ADFS Application Source under Authentication Type.
  5. Now type in the Target URL  RPID= and select NEXT
  6. Click NEXT on the Access Policies Page, and SAVE & ASSIGN on the Summary page
  7. In the Assign page assign the application to the group
  8. Start typing and you will see the Group showing up click it to confirm
  9. Now set the Deployment Type group to automatic and select SAVE

1. Close the browser and all windows to ensure firefox or chrome has closed properly. Now re-open firefox and navigate to your unique Workspace ONE Access SaaS instance.

2. Now log in as user1 user and password VMware1! in the domain you will then notice in the catalog the socialcast application.

3. Now click on Open under socialcast icon and you will be redirected to Socialcast and authenticated without additional credentials as user1.

ExtraCurricular: Setting Workspace ONE Access as the default claim provider

There might be a use-case where an organisation wants the configured relying party in ADFS always use a specific claims provider. Through powershell admins have the ability to set the default claims provider for specific relying parties.  

On the ADFS Server do the following

1. navigating to and clicking on "as employee" notice you will now have an option here to either choose Workspace ONE Access Livefire or Active directory.

2. Open powershell and type


3. You will now be able to see that socialcast is set to use both Active Directory and Workspace ONE Access LiveFire as the claims provider

4. Let's now set Workspace ONE Access as the default claims provider

 In the same power shell windows now execute the below 

Set-AdfsRelyingPartyTrust -TargetName "SocialCast" -ClaimsProviderName @("Workspace ONE Access Livefire")

5. Confirm the changes by typing the same command to get the relying party trust information. You will notice now that Workspace ONE Access Livefire is listed as the only ClaimsProvierName 


6. Now close your browser and re-open to 

7. Click on as Employee notice now that you will automatically be re-directed to Workspace ONE click Next.  After authenticated you will automatically be logged into Socialcast. Observe you weren't prompted to chose the claim provider as in the original test. In order to reverse the above simply re-add Active Directory as another claims provider. 

 Set-AdfsRelyingPartyTrust -TargetName "SocialCast" -ClaimsProviderName @("Workspace ONE Access Livefire", "Active Directory")


Add your comment

E-Mail me when someone replies to this comment