Configuring Azure for Simplelists SAML2 Authentication

Posted on (updated on )

Create an Azure Enterprise Application for Simplelists

  1. Login to your Microsoft Azure Tenant https://portal.azure.com Microsoft Azure Dashboard
  2. Click View on Manage Microsoft Entra ID or click Microsoft Entra ID

Manage Azure Active Directory

Manage Entra ID
  1. Click Enterprise applications from the left hand menu

Create a new Enterprise Application

Enterprise Applications
  1. Click New application

Create your own application

Create new application
  1. Click Create your own application Create your own Application
  2. Enter Application Details
    1. Enter the name of your app (Simplelists or other unique name)
    2. Select Integrate any other application you don’t find in the gallery (Non-gallery)
    3. Click Create

Setup single sign on

Configure Enterprise Application
  1. Click Get started under Set-up single sign on

Select a single sign-on method

Select Signon Method
  1. Click SAML

Set up Single Sign-On with SAML

The metadata file referenced below is the saml.xml file that you can download from the Simplelists Authentication provider that is created using Configuring a SAML2 Authentication Provider

The metadata file will include most of the settings required. The RelayState value is also located on the Authentication Provider created as per Configuring a SAML2 Authentication Provider

Setup single signon with SAML
  1. Click Upload metadata file Upload Metadata
  2. Click Add

Verify Basic SAML Configuration that was uploaded

Basic SAML Configuration
  1. Enter the RelayState from the Simplelists settings
  2. Click Save

The RelayState is a value that Azure will pass to Simplelists when authentication is initiated from the Azure applications page. It must match the value in Simplelists, and can be found on the Authentication Provider created in Simplelists.

Download the Metadata and Certificate for Simplelists

Save each of these files to a location to upload the the Authentication Provider Settings of Simplelists.

Download certificate and metadata.xml
  1. Click Download to the right of Certificate (Base64)
  2. Click Download to the right of Federation Metadata XML

Azure - Enable User Login

Depending on your Azure settings you may need to enable user log in for the Simplelists application in Azure.

Simplelist Enterprise Application
  1. Click Users and Groups

Users and Groups

Azure Users and Groups
  1. Click Add user/group

Add Assignment

Azure Add Assignment
  1. Click None Selected under Users

Users

Azure Select User
  1. Click on each user (or group) that you wish to add
  2. Click Select

Add Assignment

Azure Add Assignment
  1. Click Assign

Testing Login

Access the Simplelists page and click Login

Simplelists Main Login page
  • Click login Simplelists login page
  • Enter your Azure enabled email address and click submit.

    If everything is correctly configured you will be presented with the Azure login page.

    Azure Enter Account ID Pick Azure Account ID
    1. Enter the "Email address, phone number or Skype" or pick the account from the list
    2. Click Next Azure enter password
    3. Enter your password
    4. Click Sign In Azure enter 2FA code
    5. You may need to enter your two factor authentication code (2FA)
    6. Click Verify Azure Stay Logged In
    7. Choose whether you want to stay logged in
    8. Click Yes or No

Azure Optional Configuration

Azure Verification certificate

Configuring a verification certificate requires Microsoft Entra (Azure) to verify that the SAML AuthnRequest was properly signed by Simplelists with the expected certificate.

This provides your application with a little additional security as only Simplelists can correctly authenticate but it does mean that login can ONLY be initiated from the Simplelists page. You cannot initiate login from the Microsoft Entra (Azure) application list.

Shows the Enterprise Application and Certficate Verification settings
  1. Click Edit in the Verification certificates (optional) section

Verification Certificates

Verification Certificate upload settings
  1. Click Require verification certificates
  2. Click Upload certificate Select a Verification Certificate to upload
  3. Select the Simplelists signing certificate Close the Verification Certificate page
  4. Click Save
  5. Close the settings with the X.

Azure - Enable SAML Token Encryption (Optional)

SAML token encryption increases the security by fully encrypting the data sent from Azure to the web Application. The user will be unable to determine what data is in the Assertion. However, it also makes it difficult to troubleshoot because you cannot view the Assertion in the browser. Get everything else working first then decide if you want to implement this.

  1. Click Security from the left hand menu Enterprise Application - Security - Token Encryption
  2. Click Token Encryption Token Encryption - Import Certificate
  3. Click Import Certificate Ipmort the encryption certificate
  4. Select the simplelists.cer file that you can download from the Authentication Settings in Simplelists

Activate the Encryption Certificate

  1. Click on the three dot at the right side of the certificate Activate Encryption Certificate
  2. Click Activate Token Encryption Certificate

Encrypted Assertions are now enabled. However you will need to complete the next step to make it work correctly.

Sign the SAML response and Assertion (Optional)

This step is only required if you enabled token encryption.

Get everything else working first then decide if you want to implement this (and token encryption).

  1. Click Edit to the right of Token signing certificate
Shows the Enterprise Application and Certficate Verification settings
  1. Select Sign SAML response and assertion from the Signing Option drop-down
  2. Click Save
Sign Response and Assertion

Enable Automatic user creation (Optional)

For IdP initiated login you can choose to have users automatically created. Simplelists uses "Automatic user creation groups" to assign user permissions.

Modify the Authentication Provider to add group

Modify the Authentication Provider
  1. Open the Authentication Settings that you created above
  2. Click Add group

Create the new Group

Create the Authentication Group
  1. Enter a free form description (It will appear on the Authentication Provider Page)
    • Administrator
  2. Enter the SSO Group Name (that will be sent by Azure)
    • SimpleLists-Administrator
  3. Select the Account Permissions
  4. Click Create

Note that the created groups are listed under the existing groups and show the description, not the SSO group name. The SSO group name (required to match Azure’s groups) can be viewed by clicking on the group name.

Enable SAML Groups

Enable the SAML Group
  1. Set the Attribute for groupname (optional)
    • http://schemas.microsoft.com/ws/2008/06/identity/claims/groups
  2. Save the authentication provider

Note: The group attribute id might be different. It will need to match the attribute name in the SAML assertion.

Test login with a new user

At this point you can attempt to login to Simplelists from the IdP applications page. Select a user that is associated with the correct group (that does not already have a Simplelists account). The user should be automatically created.


Troubleshooting / FAQs

This section provides symptom-to-cause guidance for common issues. No new configuration steps are introduced here.

AADSTS50105: The signed in user is not assigned to a role for the application

The user hasn’t been assigned to the Simplelists enterprise application in Azure. Return to the Users and Groups section and add the user or a group they belong to.

AADSTS700016: Application with identifier ’...’ was not found

The Entity ID in the SAML request doesn’t match any application in your Azure tenant. This typically means the metadata file wasn’t uploaded correctly, or you’re testing against the wrong Azure tenant.

“Signature validation failed” or “Invalid signature”

The certificate Simplelists is using to validate Azure’s response doesn’t match Azure’s current signing certificate. Re-download the Certificate (Base64) from Azure and upload it to your Simplelists Authentication Provider.

Response destination does not match assertion consumer service URL

The Assertion Consumer Service (ACS) URL configured in Azure doesn’t match what Simplelists expects. This usually happens if the metadata file was modified or if you’re using an incorrect metadata file. Re-download and re-upload the metadata from Simplelists.

Login works from Simplelists but fails from Azure’s My Apps portal

The RelayState is missing or incorrect in Azure’s Basic SAML Configuration. Verify the RelayState value matches exactly what’s shown in your Simplelists Authentication Provider settings.

Login redirects to Azure but returns an error immediately

Multiple causes are possible: the user isn’t assigned to the application, the Entity ID is wrong, or there’s a certificate mismatch. Check the Azure sign-in logs for the specific error code and message.

After Azure certificate renewal, logins fail

Azure periodically rotates its signing certificates. When this happens, you must download the new certificate from Azure and upload it to Simplelists. Azure typically provides advance notice of certificate expiry in the Enterprise Application settings.

Users are created but have no permissions

The group mapping between Azure and Simplelists isn’t configured correctly. Verify that the SSO Group Name in Simplelists exactly matches the group identifier Azure sends (which may be a group name or an Object ID, depending on your Azure claims configuration)