Skip to main content

How to Set Up SAML Integration with MedMe

This article explains how to set up SAML integration to log in to the MedMe Platform using corporate credentials.

Written by Nick Hui

Table of Contents

Overview

SAML integration allows users to authenticate with the MedMe Platform through their organization's identity management system (e.g., Microsoft Login), eliminating the need for separate MedMe credentials for each user.

Please Note: Users will be redirected to their corporate login screen to authenticate, then returned to MedMe upon successful login.

Key Terms

Identity Provider (IdP)
A system that manages user identity and authentication.

  • Example: Azure Active Directory (Azure AD)

Security Assertion Markup Language (SAML)
A standard for exchanging authentication and authorization data between an identity provider and a service provider.

Service Provider (SP)
An application (e.g., MedMe) that relies on an IdP to authenticate users.

MedMe's SAML Setup

Service Provider (SP):

  • Amazon Cognito (used by MedMe)

Identity Provider (IdP):

  • Azure AD (most commonly used by enterprise pharmacy clients)

For Instance: A pharmacy chain using Azure AD for employee logins can connect that same system to MedMe, so staff use their existing corporate credentials instead of a separate MedMe password.

Enterprise Setup Instructions

Step 1: Create a New Enterprise Application

  1. In Azure AD, go to Enterprise Applications.

  2. Click + New Application.

  3. Select Non-gallery Application.

Step 2: Configure Single Sign-On (SSO)

  1. Choose SAML as the SSO method.

  2. In the Domain and URLs section, enter:

    • Identifier (Entity ID)

    • Reply URL (ACS)

    • Logout URL

Reminder: MedMe will send these unique values via email. Enterprise clients should not generate these values independently.

Step 3: Provide SAML Metadata to MedMe

  1. Save the SSO configuration in Azure AD.

  2. Send MedMe the following:

    • The Metadata URL

    • The Metadata XML

MedMe uses this information to finalize your integration.

Step 4: Configure Attributes and Claims

Ensure SAML assertions include the following user fields:

  • First Name

  • Last Name

  • Email

  • Store(s)

  • Role

  • License Number (if applicable)

Please Note: Configure Group Claims if using Azure AD groups for access control.

Step 5: Add Users

  1. Assign users to the new application in Azure AD to grant them MedMe access.

Step 6: Test the Integration

  1. In the Azure portal, open the application's Single Sign-On section.

  2. Click Test SAML Settings.

Tip: Verify that the login redirects, user fields, and access permissions are all functioning correctly before rolling the integration out to the full team.

Troubleshooting

Login does not redirect to the corporate sign-in screen

  • Confirm the Identifier (Entity ID), Reply URL (ACS), and Logout URL were entered exactly as provided by MedMe.

User fields (e.g., Role, Store) are missing after login

  • Check that all required fields are included in the Attributes and Claims configuration in Step 4.

A user cannot access MedMe after SSO is configured

  • Verify the user has been assigned to the enterprise application in Azure AD (Step 5).

Warning: If Metadata XML is updated on the Identity Provider side after the initial setup, notify MedMe immediately so the Service Provider configuration can be updated. Mismatched metadata will cause authentication failures.

Conclusion

SAML integration simplifies user access to MedMe through corporate credentials, enhancing both security and user management across enterprise pharmacy teams.

For related setup steps, see: How to Create and Manage a Pharmacist Account.

For assistance, contact the MedMe team at care@medmehealth.com.

Related Articles
Did this answer your question?