ADFS Proxy with O365 using SAML

My OPSWAT Central Management can be easily integrated with ADFS Proxy to ensure that a device is compliant with the organization's security policy before it is granted access to O365. This ensures that the device is not only authenticated by the IdP, but also tested for risks and vulnerabilities such as infections or unpatched versions of operating systems, BEFORE it access an organization's cloud services.

To get started with implementing My OPSWAT Central Management integration to enforce device posture check before granting a device to access O365 with ADFS Proxy, you set up SSO between AD FS server and O365 manually. You need the following requirements

  1. A domain.

  2. An Active Directory instance.

  3. Add your domain to Office 365.

  4. Install Windows PowerShell for Azure Active Directory here.

  5. Install ADFS server.

  6. Using Azure AD Connect to enable Single Sign-On to Office 365.

Configuring, installing ADFS server and enabling SSO to Office 365 is beyond the scope of this tutorial. This tutorial uses screenshots from Server 2012R2, but similar steps should be possible on other versions.

Now it's the time you can integrate My OPSWAT Central Management with your ADFS by following below steps. You can learn more details for each step here at 3.1.1. How to set it up?

Step 1. Enable Access Control on your My OPSWAT Central Management account

  1. Login to the My OPSWAT Central Management console.

  2. Navigate to Secure Access > Protected Apps.

  3. Check on the box "Enable Secure Access ".

  4. Navigate to Integrations and then Device Identity, and enable Enable cross-domain API integration at port xxxx

Step 2. Add protected applications with IdP Method

  1. The next step is importing an ADFS Signing certificate to My OPSWAT Central Management. This allows My OPSWAT Central Management to verify users signing though a trusted IdP. Each identity provider has a unique X.509 certificate. Download the ADFS Signing certificate by following these steps:

    1. Login to Windows Server

    2. Open Server Manager

    3. Click Tools

    4. Click AD FS Management

    5. Expand Service

    6. Click Certificates

    7. Double-click on the "Token-signing" being used to sign your responses


8. Click Copy to File to download the certificate. That should open another box, showing the certificate export wizard. Click Next and you will be asked which format to export the certificate in. Choose Base-64 encoded X.509


  1. Collect Idp Login URL In this case, Idp Login URL is https://login.microsoftonline.com/login.srf

  2. Add the ADFS Identity Provider. If you already have ADFS IdP settings on your My OPSWAT Central Management account, go to 4 to add O365 application.

    1. Login to the My OPSWAT Central Management console.

    2. Navigate to Secure Access and then Access Methods

    3. On the Identity Providers tab, click "Create New Identity Provider" to add your IdP

    4. Fill in required fields for the Identity Provider

      1. IdP Name: an IdP name, for example: ADFS

      2. IdP Certificate: upload ADFS certificate you downloaded in Step 2.1

  3. Click SAVE.

  4. Add the O365 application:

    1. Expand the ADFS IdP settings you have just added in Step 2.3 above.

    2. Navigate to Secure Access and then Protected Apps. Click Add New Application.

    3. Select IdP Method and choose from the existing IdPs, finding the one you just made. Press Continue.

    4. Enter required field

      1. Application: application name, for example: O365

      2. IDP Login URL: application login URL which you have from Step 2.2

      3. Login URL: https://login.microsoftonline.com/login.srf

      4. Logout URL: https://login.microsoftonline.com/logout.srf

      5. Access Mode: pick an access mode you prefer. See details on the access modes at Step 2. Add protected applications with IdP Method

      6. Click Add

      7. After saving your changes successfully, click the Setup Instructions button of the O365 application you have just added and then copy the URL My OPSWAT Central Management generated there. This URL is used to replace O365 login URL on ADFS.

      8. Download the Note: you can add O365 application (step 2.4) when you add ADFS IdP settings.

Step 3. Configure Access Rules

  1. On My OPSWAT Central Management console, navigate to Secure Access and then Rules

  2. Click "ADD NEW RULE" to add a new rule for this application OR you can update existing access rules to add this application

  3. With a new access rule, you need to specify how you would like to block/allow access a device from the application

    1. Rule name: a rule name, for example Block non-compliant devices

    2. Action: Block or Allow

    3. Configure conditions to do the action. Details at Step 3. Configure Access Rules

  4. Click ADD RULE

Step 4. Update Office 365 Relying Party Trusts in AD FS Server

  1. Update Passive Endpoint

    1. Login to Windows Server

    2. Open Server Manager

    3. Click Tools

    4. Click AD FS Management

    5. Expand Trust Relationships

    6. Click Relying Party Trusts

    7. Double-click on "Microsoft Office 365 Identity Platform" and choose Endpoints tab


8. Click Add SAML to add new Endpoint

9. Use the URL in step 2.5 as Trusted URL:


10. Click OK

  1. Configure the Active Directory claims-provider trust

    1. Right-click "Microsoft Office 365 Identity Platform" and choose Edit Claim Rules


2. On the Issuance Transform Rules tab, click Add Rule


3. In the Claim rule template box, select Send Claims Using a Custom Rule, and then click Next


4. In the Claim rule name box type "Issue nameidentifier SAML 2.0", and fill the Custom rule as follow:

c:Type == "[http://schemas.microsoft.com/LiveID/Federation/2008/05/ImmutableID"] => issue(Type = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Value = c.Value, Properties"[http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] = "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent");


5. Click Finish

6. Click OK


Step 5. Edit SSO settings on Office 365

After install and configure AD FS server, it will enable SSO for your domain, but you need to replace SigningCertificate in SSO setting to work with My OPSWAT Central Management

  1. Login to Azure Active Directory via Windows PowerShell

    1. Login to a computer installed Windows PowerShell for Azure Active Directory

    2. Start PowerShell and run Connect-MsolService cmdlet and enter your administrator credentials for your Office 365 domain when prompted

C:\Windows\system32>Connect-MsolService

  1. Backup current SSO settings

    1. Run Get-MsolDomainFederationSettings -DomainName <your domain> cmdlet to get current SSO setting

    2. Get these information

      1. FederationBrandName

      2. IssuerUri

      3. LogOffUri

      4. PassiveLogOnUri

  2. Update existing current setting

    1. Run following cmdlet

C:\Windows\system32>Set-MsolDomainAuthentication -DomainName <your domain> -Authentication Managed

2. Run Set-MsolDomainAuthentication cmdlet

C:\Windows\system32>Set-MsolDomainAuthentication ` -FederationBrandName <FederationBrandName> ` -DomainName <Your Domain> ` -Authentication Federated ` -IssuerUri <Issuer> ` -PassiveLogOnUri <Passive Endpoint> ` -LogOffUri <LogOffUri> ` -PreferredAuthenticationProtocol SAMLP ` -SigningCertificate <OPSWAT Certificate in step 2>

Note: enter the certificate on a single line without break line

3. Run following cmdlet to verify configuration

C:\Windows\system32>Get-MsolDomainFederationSettings -DomainName <Your Domain>

Note: It can take some time for Office 365 to apply new configuration

Step 6: Test your integration

Follow guideline at Step 6: Test your integration to test your integration to verify if it works as your expectation.

DONE! CONGRATULATIONS.

Next to read:
ADFS Proxy with O365 using WS-Federation
null
On This Page
ADFS Proxy with O365 using SAMLStep 1. Enable Access Control on your My OPSWAT Central Management accountStep 2. Add protected applications with IdP MethodStep 3. Configure Access RulesStep 4. Update Office 365 Relying Party Trusts in AD FS ServerStep 5. Edit SSO settings on Office 365Step 6: Test your integration