Azure AD with EasyTerritory: Cloud Hosted

Executive Overview:

EasyTerritory supports Azure Active Directory (Azure AD) capability.  Azure AD is a single sign on feature that enables a user to login to the EasyTerritory application through Azure AD.  Azure AD will authenticate the user using Active Directory credentials and direct him to EasyTerritory to access the application.


The advantages of leveraging Azure AD with your EasyTerritory application are:

  • – Simple streamlined SSO access to your EasyTerritory application through company’s IdP portal.
  • – Strengthens security with users not needing to remember additional usernames and passwords.
  • – Ability for companies to control users’ access to EasyTerritory within their active directory.

Technical Overview:

EasyTerritory supports Azure AD with the SAML (Security Assertion Markup Language) XML framework for authenticating users who are wanting to connect to EasyTerritory.

It is important to note that EasyTerritory’s SAML configuration is Ipd-Initiated, which means when a user attempts to browse to EasyTerritory they will be redirected to his company’s Azure AD sign-on page.

When a user is authenticated through Azure AD, a token will be sent to the EasyTerritory servers. EasyTerritory will receive the token and grant access based on the credentials and authenticity of the claims in the token.

Client-Side Configuration:

These are details for setting up adfs on your active directory servers.

  • The information you will need when setting up an Azure AD Enterprise Application:
    •  – Relying Party’s identifiers:
      • EasyTerritory GUID here/APP/
    • – SAML consumer Endpoints (Reply URL):
      • EasyTerritory GUID here/APP/AuthServices/Acs
        • This uri will redirect you after you have been authenticated by your IdP.
  • Claims:
    • EasyTerritory requires a username, first name, last name and email when authenticating claims that are sent. These claims must match on your server and EasyTerritory’s server.  You can decide what to call the claims, but those claims must be sent to an EasyTerritory administrator. Please note that there are two alternatives for userNameClaim and emailClaim.
    • Here are some examples:
      • – User Name Claim:
      • – First Name Claim:
      • – Last Name Claim:
      • – Email Claim:
  • Azure AD URI’s
    • Information an EasyTerritory administrator will need when configuring your EasyTerritory application are entity Id, the sign-on URL, and logout URL. Here are some examples.
      • – Server’s entity Id:
        • https://sts.[]/[identifyingGuid]
      • – IdP sign- on URL:
        • https://[Your Azure AD Endpoint]/[IdentifyingGuid]/ saml2?SAMLRequest=[deflated, base-64 encoded, URI-encoded SAML request]
          • EasyTerritory will generate the SAMLRequest that is appended to the above URL.
      • – Log out URL:
        • https://[Your Azure AD Endpoint]/[IdentifyingGuid]/saml2
  • We also need to know whether you need EasyTerritory to generate logout requests (and if so, whether you want them signed) or whether we can simply redirect to the bare logout URL (which is the more common scenario).
  • Certificate:
    • In order to authenticate the claims sent to EasyTerritory, EasyTerritory will need a signing certificate.
    • Download metadata from the ‘single sign-on’ blade in the Azure Portal.  Then send it to an EasyTerritory administrator.  From there an EasyTerritory admin will configure a certificate and post it on the EasyTerritory servers.


Please understand we are not Azure AD administrators. We may be able to give you some support with setting up an Azure AD application, but ideally your staff will be knowledgeable about this and we will not be involved with Azure AD configuration on your end.