OneLogin
OneLogin Inc. is a cloud-based identity and access management (IAM) provider that designs, develops, and sells a unified access management system (UAM) platform to enterprise-level businesses and organizations. Founded in 2009, by brothers Thomas Pedersen and Christian Pedersen, OneLogin is a late stage venture, privately held company. The OneLogin UAM platform is an access management system that uses single sign-on (SSO) and a cloud directory to enable organizations to manage user access to on-premises and cloud applications. The platform also includes user provisioning, lifecycle management, and multi-factor authentication (MFA).
Supervisor configuration parameters
To configure the connector, following parameters are required:
Supported objects and operations
Users
Table 110: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Delete User |
DELETE |
Get User by id |
GET |
Get All Users |
GET |
Get All Users with pagination |
GET |
Groups
Table 111: Supported operations for Groups
Get Group by id |
GET |
Get All Groups |
GET |
Get All Groups with pagination |
GET |
Roles
Table 112: Supported operations for Roles
Get Role by id |
GET |
Get All Roles |
GET |
Get All Roles with pagination |
GET |
Mandatory fields
This section lists the mandatory fields required to create a User or a Group:
Users - Create
-
userName
-
name.givenName
-
name.familyName
- emails.value
Users - Update
userName or emails.value
Groups
Not Applicable
Mappings
The user and group mappings are listed in the tables below.
Table 113: User mapping
Id |
Id |
UserName |
username |
ExternalId |
external_id |
Name.GivenName |
firstname |
Name.FamilyName |
lastname |
Name.Formatted |
firstname +" " + lastname |
DisplayName |
firstname +" " + lastname |
Emails[0].Value |
email |
PhoneNumbers[0].Value |
phone |
Title |
title |
Roles[].Value |
role_id[] |
Groups[0].value |
group_id |
Active |
status |
Locale |
locale_code |
Extension.Manager.Value |
manager_user_id |
Extension.Organization |
company |
Extension.Department |
department |
Extension.OpenIdName |
openid_name |
Extension.DistinguishedName |
distinguished_name |
Extension.SamAccountName |
samaccountname |
Extension.UserPrincipalName |
userprincipalname |
Extension.MemberOf |
member_of |
Extension.DirectoryId |
directory_id |
Meta.Created |
created_at |
Meta.LastModified |
updated_at |
Groups
Table 114: Group mapping
Id |
id |
DisplayName |
name |
Roles
Table 115: Role mapping
Id |
id |
Name |
name |
Connector limitations
Creating a service account in G Suite
Creating a service account in G Suite
You must obtain a JSON file with Private Key to authorize the APIs to access data on
G Suite domain. Create and enable the service account to obtain the private key (JSON file).
To create a project and enable the API
-
Login to Google Cloud Platform.
-
Click on the drop-down list next to the Google Cloud Platform label and select an organization.
The Select a Project window is displayed.
- Click New Project.
The New Project page is displayed.
-
Enter the specific details in the relevant text field.
- Click Create.
-
Click on the drop-down list next to the Google Cloud Platform label and select the project you created.
-
Click APIs & Services tab.
- Click Library tab.
-
Search for the phrase Admin SDK in the search bar and select Admin SDK from the results.
The API Library page is displayed.
- Click Enable to enable the API.
To create a service account
-
Click APIs & Services tab.
- Click Credentials.
-
On the Credentials tab, click Manage Service Accounts available at the bottom right corner.
The Service Accounts window is displayed.
-
Click + CREATE SERVICE ACCOUNT.
Create service account window is displayed.
-
Enter the name of the service account in Service account name text field.
- Select Owner as the Role from the drop-down menu.
-
Select the service JSON as an account Key type.
IMPORTANT: A JSON file is required to generate an access token and it is downloaded automatically after selecting the above option.
- Click Create.
To select and authorize the API scopes
-
Login to the G Suite admin console with your domain.
-
On the Admin console home page, click Security.
-
Click Advanced settings.
-
Click Managed API client access.
-
Enter the client name and the description in the Name and Description text field respectively.
-
Enter the email in the Email text field.
-
Add the preferred API scopes that you want to use.
For example, API scopes can be https://www.googleapis.com/auth/admin.directory.user, https://www.googleapis.com/auth/admin.directory.group, or https://www.googleapis.com/auth/admin.directory.group.member.
For more information on API scopes, see https://developers.google.com/identity/protocols/googlescopes
- After adding the API scoes, click Authorize.
The unique Id and the scopes added is displayed.
Setting a trial account on Salesforce
Setting a trial account on Salesforce
To login to the Saleforce application, you must create a trail account. The sections below briefs about the process to create a trial account .
To setup a trial account
-
Login to the Salesforce developer edition link: https://developer.salesforce.com/signup?d=70130000000td6N.
- Provide the relevant details and click Sign me up.
A trail account is created and an instance is assigned.
- Switch the view to Saleforce classic view by clicking Switch to Salesforce Classic.
- Click the Setup tab.
- Click Build | Create | Apps.
- In the Connected Apps section, click New.
- In the Basic Information section, enter the relevant details.
- In the API (Enable OAuth Settings) section, select Enable OAuth Settings checkbox.
- Provide the https://app.getpostman.com/oauth2/callback URL in the Callback URL text field.
- From the Selected OAuth Scopes drop-down menu, select Full Access (full).
- Click Save.
- From the API (Enabel OAuth Settings) section, retrieve the Consumer Key and Consumer Secret.
To generate a security token
A security token is sent to the registered email address. If not received, follow the below steps to generate a token.
-
On the home page, click My Settings.
- Click Personal | Reset My Security Token.
- Review the information displayed on the screen and click Reset Security Token.
- Provide the relevant information such as:
IMPORTANT: Replace this text with a notation that requires the reader's attention.
Working with Azure Active Directory
Working with Azure Active Directory
The following procedure briefs about the steps to register application, provide appropriate permissions, retrieve client ID, and client secret.
Working with Azure AD
-
Login to the Microsoft Azure portal and select Azure Active Directory from FAVORITES.
- From Manage section, select App Registrations (Preview).
NOTE: For Safeguard for Privileged Passwords, the Azure AD application registration must be public.
- Click New registration and provide the necessary details.
Provide the following details:
- Select the created application and click View API Permissions.
- Add the required permissions for Microsoft Graph API (delegated and application permissions).
The registered application must have User.ReadBasic.All, User.Read, User.ReadWrite, User.ReadWrite.All, Directory.Read.All, Directory.ReadWrite.All, Directory.AccessAsUser.All, Group.Read.All, and Group.ReadWrite.All permissions.
- Click Grant admin consent for Default Directory checkbox to grant necessary permissions.
- From the created application, click App Registrations (Preview) and note the Application (client) ID and Directory (tenant) ID.
- Select Certificates & secrets and click New client secret to generate the secret.
- Paste the following URL in the browser, https://login.microsoftonline.com/common/adminconsent?client_id={Client ID}&state=12345&redirect_uri=http://localhost/myapp/permissions.
- Click Accept.
Providing permission to update or delete users password
-
Install the Azure AD PowerShell v1 module (MSOnline).
-
Connect to your Azure AD B2C tenant.
-
Use the Application(client) ID in the PowerShell script to assign the application the user account administrator role.
For more details on Azure AD, refer the following links: