Skip to end of banner
Go to start of banner

Creating a User

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

In this article

Overview

Use SnapLogic Manager or User and Group APIs to add users to your Org. A new user receives a sign-up email from SnapLogic, with a generated password.

Refer to the AutoSync documentation for more information on AutoSync users.

User Types

You can use the Create User dialog to create the following types of users in Manager:

  • Basic user—Logs in to SnapLogic applications using a username and password. 

  • Basic user (SSO Login)—Logs in to SnapLogic applications through an SSO (Single Sign-On) configured for the Org and has access the UI, not directly through the SnapLogic UI login. Use the Disable Password-based Login in the Create User dialog for this option.

  • Basic user (No UI Access)—Does not log in to the SnapLogic IIP UI but has access to SnapLogic assets. Select API Access in the Create User dialog for this option. A regular user without UI access can act as a service account, but the user receives password reset emails.

  • Org admin—Administers Org Settings, manages feature subscriptions, and has access to all assets in the Org. You must belong to the admins group to be an Org admin.

  • Service Account—Does not log in to the SnapLogic IIP UI and can only run Triggered Tasks with basic authentication. Service accounts require permissions on a project or group basis, like regular user accounts. These accounts, however, cannot access Designer or Manager, and can only run Triggered Tasks with basic authentication. The user that creates a service account will receive the welcome email for that service account. 

Additional Options

  • You can create a project name that reflects the user name. The project offers 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.
  • You can make a user an Org Administrator by adding that user to the admins group.
  • You can also disable email notifications to users when you create them. This option can be used for user types that do not require access to the UI or if the user logs in through an SSO. 
  • To work with the Manage Password Logins dialog box, you should have enabled SSO in your Org.

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.

Steps

  1. In the SnapLogic Manager, click Users in the navigation pane to display the Users screen.

  2. In the toolbar of the Users screen, Click create  icon.

    The Create User dialog box is displayed.

  3. In the User Email field, enter the email ID.



    1. To create a project for this user in the default projects space, select Create a project for this user in the default project space.

    2. To provide Org admin permissions to this user, select Provision this user as an Org admin.

  4. Click Next. The dialog box displays the details required to create the user.

    1. Enter the First name and Last name of the new user.

    2. Select the Send notification emails option to send a welcome email when the user is created.

      SSO Login

      • If you use Single Sign On (SSO) for login, you can disable this setting. If this option is disabled, then as an Org admin you would provide account information directly to a new user, since the welcome email that contains the user's login information is not auto-generated. 
      • Click the to help icon  to view the context sensitive helop.

      • Click the help icon  to view the help documentation.

    3. If you plan to use SSO and do not want the users to have a separate SnapLogic login, select Disable password-based login .
      For information on managing password-based logins for existing users, see Manage Password Logins.

  5. Click Next. The dialog box displays the options for the account access.



  6. Specify the access in the Assign Account Access dialog:

    1. Application Access
      • Intelligent Integration Platform (IIP)
      • AutoSync, if provisioned for the Org,  AutoSync V1.0 (deprecated) might appear in Orgs where it was previously provisioned.
    2. Select API Access Only to prevent the new user from logging in. 
      This option is grayed out for service accounts. 
      This setting applies to all Orgs to which the user is associated. 

      This setting applies to all Orgs to which the user is associated.

    3. Select Provision this user as a service account (web login disabled) to create an account to call Triggered Tasks. Credentials for this user are sent to the account creator, as are all reset password emails. You can change a service account into a regular user account by updating the user and deselecting this check box.

  7. To encrypt the new user's emails, upload a public key. Currently, only .der and .pem file types are accepted.
    Encrypted emails are locked and can only be unlocked with a private key. 

    This option is only visible if Email Encryption is enabled in the Org Settings. 

  8. To add the user to the Org, click Create.

Associate a Service Account with another Org admin

You can use the Public API to associate a service account to another Org admin by setting the created_by attribute to the new user. The following example shows an HTTP request that can update the service account.

Guidelines:

  • You can make the request using Postman.
  • You  can authenticate the request using Org admin credentials
  • Make sure that you specify in the HTTP header the Content-Type: application/json
     

API Call:

PUT https://elastic.snaplogic.com/api/1/rest/public/users/jasper_doe@example.com

{

  "first_name" : "Jasper",

  "last_name" : Doe",

  "allow_password_login" : true,

  "revoke_old_password" : true,

  "utility" : true,

  "ui_access" : false,

  "created_by" : "admin92@example.com"

}

Learn more about how to use Public APIs to Update a User.

Related Content:


  • No labels