Skip to main content
McAfee Enterprise MVISION Cloud

Integrate MVISION Cloud for Salesforce with ADFS and SAML Proxy

You can configure Single Sign-On using ADFS for Salesforce and the MVISION Cloud SAML proxy.

As Salesforce issues an Assertion Consumer Services (ACS) in the SAML request to the identity provider (IdP), you must use the SAML proxy for both the SAML request from Salesforce and the SAML assertion from ADFS.

NOTE: An ACS is really where the service provider (SP) wants to receive the SAML assertion. It is a web-based service that waits to receive SAML formatted messages. It is sometimes also referred to as a login URL or an endpoint.

Other terms used in this topic:

  • SP. The Service Provider.
  • IdP. The Identity Provider.
  • Entity. This is what the SP calls itself when it presents the request to the IdP. The IdP must have a record of the entity to accept the request.
  • Issuer. This is what the IdP calls itself when it presents its assertions to the SP. The SP must have a record of the issuer to accept the response.


Configuration Before MVISION Cloud


Configuration After MVISION Cloud


NOTE: for some services like Office 365, it is not necessary for MVISION Cloud to proxy the SAML request. For Salesforce, however, this is required as SFDC includes their ACS in their SAML request. MVISION Cloud needs to change this before it gets to the IdP, otherwise the SAML response will bypass MVISION Cloud.


The following prerequisites are required:

  • Add a Salesforce instance with a vanity domain.
  • Configure the MVISION Cloud reverse proxy for Salesforce (without SSO).
  • A functioning ADFS server that is publicly available on the Internet with a valid SSL certificate and DNS resolvable hostname.
  • User(s) in AD and in Salesforce that line up. (There is no automated user provisioning in this configuration.)

Collect the Required Information

Collect the following information from MVISION Cloud and Salesforce:

  1. MVISION Cloud Salesforce reverse proxy domain alias. 
  2. MVISION Cloud SAML proxy certificate. 
  3. Salesforce vanity domain. In Salesforce, go to Setup > Domains
  4. Salesforce request signing certificate. In Salesforce, go to Setup > Certificate and key management, then download the certificate. 
  5. Salesforce Login URL. In Salesforce, go to Setup > Single Sign On
  6. ADFS SAML 2 endpoint. This is where the SAML request will be sent (via the SAML proxy). https:// <ADFS FQDN> + /adfs/ls
  7. ADFS token signing certificate. In ADFS, go to Certificates > Token signing > View Certificate. Then select the Details tab, and export to file. Export to base 64.
  8. ADFS federation service identifier (issuer). In ADFS, right-click ADFS > Service and select Edit Federation Service Properties

NOTE: Make sure the federation service name matches the FQDN of the public DNS record and SSL cert.


Configure MVISION Cloud

  1. Log in to MVISION Cloud and go to Settings > Service Management. Select your Salesforce instance. 
  2. Find the Reverse Proxy Properties. 
  3. Either make sure you already have, or add a custom.domain property that maps to your Salesforce vanity domain. You will use this value later, just remember the last part of the property name (vanity) and not the entire property name (custom.domain.vanity).

NOTE: You should only configure one custom.domain.XXXX property with the value of your vanity Salesforce domain. If you have >1 property with this configured, you will need a separate ADFS endpoint for EACH property set to the vanity domain. 

  1. Configure the SAML proxy. 

Configure Salesforce

  1. Create a new SSO configuration (settings > single sign-on)
    • Issuer. ADFS Federation Service Identifier (example:
    • Identity provider certificate. The MVISION Cloud SAML proxy certificate
    • Request a signing certificate. The certificate you exported from SFDC and uploaded to MVISION Cloud SAML proxy as the service provider cert
    • Request signature method. RSA-SHA1
    • Entity ID.
    • Identity provider login URL. <vanity mapping><MVISION Cloud Salesforce reverse proxy domain alias>/domain-access?shnsaml-request=<URL encoded version of the ADFS login endpoint>
    • Example:
    • Identity provider logout URL. <FQDN ADFS>/adfs
  2. Download the SFDC SSO metadata. 

Configure ADFS

  1. Create a new Relying Party Trust.
  2.  Upload the SFDC metadata file. 
  3. Enter a display name.
  4. Permit everyone to use this app.
  5. Hit next after verifying the data that has been imported using the metadata file. 
  6. Edit the new app's properties.
  7. On the signatures tab, delete the Salesforce certificate and replace it with the SAML proxy certificate. 
  8. On the advanced tab select SHA1. 
  9. On the Endpoints tab, edit the edit the endpoint as follows:
    • Original:
    • New:

NOTE: vanitycrm will map to the custom.domain.vanity value you added earlier in the reverse proxy properties. This allows the SAML proxy to receive the SAML assertion from ADFS and then forward it onto the vanity URL in Salesforce.

  1. Edit the Claim Issuance Policy (or edit the Claim Rule - same thing just Microsoft change the name).
  2. Select Add Rule and configure the following:
    • Send LDAP attributes as claims
    • Name. Send nameID as UPN.
    • Attribute store. Active Directory.
    • Mapping. User-Principal-Name = Name ID


If you don't already have a SAML decoder, download this one:

  1. Connect to your Salesforce instance and login using SSO (ADFS profile).
  2. With your SAML decoder, review the first SAML request. This is the one from SFDC to the SAML proxy.
    • AssertionConsumerServiceURL. Direct to SFDC
    • Destination. MVISION Cloud SAML proxy
  3. Review the second SAML request, this is the one the SAML proxy has rewritten and the one ADFS receives.
    • AssertionConsumerServiceURL. MVISION Cloud Reverse Proxy
    • Destination. ADFS
  4. Log in using your ADFS account. Remember, you must have the same user in SFDC as well.
  5. Post login you should be directed to SFDC via the MVISION Cloud reverse proxy.
  6. Review the SAML response. Destination is the MVISION Cloud reverse proxy.
  • Was this article helpful?