End-to-end testing Identity Management (SCIM) with Microsoft Azure Active Directory

Schedule a Demo

System for Cross-domain Identity Management (SCIM) is a system designed to make managing a single user identify across multiple cloud-based devices easier. SCIM is an essential element of managing multiple applications in a secure way, and is often a hard requirement in large enterprise software contracts.

SCIM with Microsoft Azure Active Directory can be a pain to test end-to-end for a variety of reasons:

  • Testing SCIM end-to-end with Microsoft Azure Active Directory introduces a dependency on both Microsoft Azure Active Directory's authentication experience, as well as the UI for provisioning or de-provisioning users using Microsoft Azure Active Directory. If the service updates the authentication or provisioning UI, you may need to update your tests.
  • Testing Microsoft Azure Active Directory SCIM involves managing multiple users and multiple sets of credentials (one for the Microsoft Azure Active Directory admin and one for the test user), which can be a pain to maintain.
  • Testing SCIM end-to-end has many edge-cases to consider. You need to verify that granting access to a third-party app provisions that user, but also that removing access to the third-party app de-provisions that same user.

What's the easiest way to test SCIM with Microsoft Azure Active Directory?

walrus.ai enables engineers to test SCIM using Microsoft Azure Active Directory without any of the pain:

  • When Microsoft Azure Active Directory's UI changes, walrus.ai handles any updates needed on their end, so you never need to refactor your tests based on any third-party dependency outside of your control.
  • Writing the full end-to-end test takes minutes, because it's just written in plain English.
  • walrus.ai can handle multiple user identities out-of-the-box. Simply add the credentials as variables, and walrus.ai can call those credentials.
  • walrus.ai can handle multiple sets of cookies, so you never have to worry about storing different sets of cookies for different users in your test case.
  • walrus.ai can handle any test setup or teardown within the test itself, simply add those steps to the test instructions.

A couple one-size-fits-most end-to-end tests for Microsoft Azure Active Directory using walrus.ai:

1---
2name: 'Microsoft Azure Active Directory SCIM'
3url: 'https://your-site.com'
4variables:
5 SCIM_provider_URL: 'https://your-site.Microsoft Azure Active Directory.com/app/UserHome'
6 SCIM_provider_admin_email: 'Microsoft Azure Active Directory_email@your-site.com'
7 SCIM_provider_password: 'Microsoft Azure Active Directory_password'
8 your_app_user_email: 'your_app_email@your-site.com'
9instructions:
10 - 'Login to :SCIM_provider_URL: with :SCIM_provider_admin_email: and :SCIM_provider_password:'
11 - 'In Microsoft Azure Active Directory, verify provisioning to App is enabled'
12 - 'In Microsoft Azure Active Directory, add :your_app_user_email: user to the your_app application'
13 - 'Login to your_app with :SCIM_provider_admin_email: and :SCIM_provider_password:'
14 - 'In your_app, verify :your_app_user_email: is added to the organization'
15 - 'In Microsoft Azure Active Directory, change the name of :your_app_user_email:'
16 - 'In your_app, verify the name of :your_app_user_email: is updated'
17 - 'In Microsoft Azure Active Directory, remove :your_app_user_email: user from the your_app application'
18 - 'In your_app, verify :your_app_user_email: is removed from the organization'

Ready to start testing SCIM with Microsoft Azure Active Directory?