CVE-2024-3400: PAN-OS Command Injection Vulnerability in GlobalProtect Gateway. Learn More

CVE-2024-3400: PAN-OS Command Injection Vulnerability in GlobalProtect Gateway. Learn More

Services
Capture
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

twi-managed-portal-color
Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

twi-briefcase-color-svg
Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

tw-laptop-data
Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

twi-database-color-svg
Database Security

Prevent unauthorized access and exceed compliance requirements.

twi-email-color-svg
Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

tw-officer
Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

tw-network
Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Microsoft Exchange Server Attacks
Stay protected against emerging threats
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
 

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 Trustwave 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.

Trustwave MailMarshal Cloud KB article Q21192

Last Modified: February 7, 2024

 Turn On Turn Off Highlight