...
- Create a project for this user in the default project space: The new project provides a workspace to build and test Pipelines without affecting other shared projects in the Org. If your company has already defined multiple Orgs in SnapLogic, and this user exists in another organization or was previously removed, then the existing user is added to the current Org.
- Provision this user as an Org admin: The new user will have administrative privileges.
- Send notification emails: Disable for account types that do not require access to the UI and for users who log in using SSO.
- Disable password-based login: The user can log in using SSO. SSO must be enabled for the Org and the user cannot belong to another Org that does not have SSO.
- Multi-factor authentication-one time passcode: The user will need to have an authenticator app and log in using the passcode it provides. If the user belongs to multiple Orgs, they will need to use MFA for all of them. <x-ref new page that describes how a user sets it up> Password-based login must be enabled. Currently, the user cannot belong to more than one Org.
Security
To protect user accounts, SnapLogic offers additional security with Multi-factor authentication (MFA) and Single Sign On (SSO). Both reduce risks of unauthorized access, phishing, and other forms of cyber-attacks. SnapLogic supports SSO for Identity Providers (IdPs) that use the Security Assertion Markup Language 2.0 (SAML 2.0) standard. SnapLogic uses Auth0 to support MFA for authenticators that comply with the OAuth 2.0 standard. We support MFA with a one-time passcode.
MFA is an optional add-on. Currently, you can only enable MFA in Classic Manager. An Org admin enables MFA per user, and the user completes the setup:
An Org admin creates or edits a user account in Classic Manager and selects Multi-factor authentication-one time passcode.
The user must create a password and register SnapLogic with their authenticator. This is a multi-step process.
Prerequisites
- You must be an Org admin to create users.
Username must be a valid email address and must meet the following requirements:
It must start with a letter, number, or one of the following special characters: !#$%&'*+/=?^_`{|}~-
The name part of the email address (before @) can contain one or more periods. The period must be followed by a letter, number, or one of the following special characters: !#$%&'*+/=?^_`{|}~-
- The domain name (after @):
- Must begin with a letter or number.
- Can contain a hyphen. The hyphen must be followed by a letter or a number.
- Must contain at least one period.
- Must end in an extension that contains at least two characters.
...