Signals Notebook: Managing User Account Transition When Implementing SSO/SAML

When implementing SSO/SAML authentication in Signals Notebook, organizations must properly manage the transition of existing user accounts to ensure continued access. This article outlines the necessary steps when email domains will change during SSO implementation.

Solution:

1. Before enabling SSO:

   • A Signals Notebook administrator must update all user email addresses in the system to match the email addresses configured in the SSO provider.
   • Navigate to the user management section in Signals Notebook and modify each user's email address.
   • Note that changing a user's email address will trigger an automated password reset email to the new address.
   • Users must set up new passwords through these emails before SSO is enabled.

2. Administrator accounts:

   • Ensure administrator accounts are updated with the correct SSO email addresses before enabling SSO.
   • Administrator privileges will be maintained after logging in through SSO.

3. SSO Configuration:

   • Follow the appropriate guide based on your identity provider:
     • For Microsoft Azure/Entra ID: See Signals Notebook SAML Authentication using Microsoft Azure/Entra ID documentation
     • For Okta: See Signals Notebook SAML Configuration with Okta documentation

4. Important considerations:

   • The email addresses in Signals Notebook must exactly match those in the SSO configuration.
   • Creating new accounts with different email addresses will result in completely new accounts, not linked to existing user data.
   • For contingency planning, consider setting up alternative authentication methods in case of SSO failure.