NewMCP ServerView docs
Security

SSO & SAML

Configure Single Sign-On with SAML 2.0 for enterprise authentication.

8 min readUpdated 2026-01-17

SSO & SAML

Configure enterprise single sign-on using SAML 2.0.

Supported Providers

  • Okta
  • Azure Active Directory
  • Google Workspace
  • OneLogin
  • PingIdentity
  • Custom SAML IdP

Setup Steps

1. Configure Your IdP

Add LH42 as a SAML application in your IdP:

SettingValue
ACS URLhttps://app.lakehouse42.com/auth/saml/callback
Entity IDhttps://app.lakehouse42.com
Name IDEmail address

2. Configure LH42

Go to Settings > Security > SSO:

  1. Upload IdP metadata XML, or enter manually:

- IdP SSO URL

- IdP Entity ID

- X.509 Certificate

  1. Configure attribute mapping:

- email → User email

- firstName → First name

- lastName → Last name

- groups → Role assignment (optional)

3. Test Connection

Click "Test SSO" to verify configuration.

Okta Setup

  1. Add new SAML app in Okta Admin
  2. Use SAML 2.0 settings
  3. Configure attribute statements:
email → user.email
firstName → user.firstName
lastName → user.lastName
  1. Download metadata XML
  2. Upload to LH42

Azure AD Setup

  1. Register new Enterprise Application
  2. Set up SAML single sign-on
  3. Configure Basic SAML settings with LH42 values
  4. Copy Federation Metadata URL
  5. Enter in LH42 SSO settings

Enforcing SSO

Once configured, enforce SSO for all users:

python
client.settings.update({
    "sso_required": True,
    "allowed_email_domains": ["yourcompany.com"]
})

Troubleshooting

"Invalid signature": Ensure certificate is correctly formatted

"User not found": Check email attribute mapping

"Access denied": Verify user is assigned to the app in IdP