LevelBlue Completes Acquisition of Cybereason. Learn more

LevelBlue Completes Acquisition of Cybereason. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
  1. Support
  2. MailMarshal Cloud
  3. Knowledge Base

HOWTO: Using ADFS/SAML Single Sign On for the Web Console

 

This article applies to:

  • MailMarshal Cloud
  • Customer Web Console

Question:

  • How do I configure Single Sign On for the Web Console?
  • Can I use AD, Azure, or G Suite logins to authenticate users to the Web Console?

Response:

MailMarshal Cloud supports SAML 2.0 SSO for the Web Console. 

You can use any compliant SAML source.

SSO for the Web Console is only used to authenticate system logins that have been created in the Web Console. Self provisioning is not supported.

For details of procedure with ADFS, Azure AD, and Google directories, see the linked documents.

The general instructions for any SAML 2.0 compliant provider are:

Procedure

  1. In the MailMarshal Cloud Customer Console, navigate to Security Configuration > Single Sign On > Console Identity Provider
  2. Click Provider Metadata to download an XML file containing the metadata definitions. This file can be imported to the provider. Alternatively, when you add or edit a provider, the Entity ID and ACS URL display and can be copied.
    • Note that these settings may be case sensitive, depending on the specific provider.
  3. Complete configuration of SSO on the provider side.
    • Ensure that you have enabled at least one user for SSO on the provider side. The user name must match the login name on the provider.
  4. In the MailMarshal Cloud Web Console, enter the details given by the provider: the Entity ID, the SSO URL, and the SSL certificate.
    • Note: The "Entity ID" information is supplied by the Identity Provider. Do not use the Entity ID copied from the MailMarshal Cloud site.
      • Providers may also refer to this value as the "SAML Issuer ID", "Federation Service identifier", or "Azure/Entra AD Identifier"
    • IMPORTANT: Take a note of the expiration date of the SSL certificate. You must create and upload a new certificate before the old one expires.
  5. After saving the provider data, you can enable Single Sign On.
    • Caution: If the provider data is incorrect, no users in your organization will be allowed to log in. Before logging out of the session where you configure SSO, test using a different account.
    • If unable to log in due to incorrect SSO settings, contact LevelBlue or your reseller.
  6. When ready to deploy SSO, enable all required groups or users for SSO on the provider side

Notes:

  • You can use the same Identity Provider for Web Console and SQM SSO by entering multiple Entity IDs and ACS URLs on the provider side. Access to the Web Console is always limited to logins that have been explicitly created.

MailMarshal Cloud KB article Q21192

Last Modified: February 7, 2024

 Turn On Turn Off Highlight