Starling Connect Identity Manager Integrated - Administration Guide

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

  1. Login to Google Cloud Platform.

  2. Click on the drop-down list next to the Google Cloud Platform label and select an organization.

    The Select a Project window is displayed.

  3. Click New Project.

    The New Project page is displayed.

  4. Enter the specific details in the relevant text field.

  5. Click Create.
  6. Click on the drop-down list next to the Google Cloud Platform label and select the project you created.

  7. Click APIs & Services tab.

  8. Click Library tab.
  9. Search for the phrase Admin SDK in the search bar and select Admin SDK from the results.

    The API Library page is displayed.

  10. Click Enable to enable the API.

To create a service account

  1. Click APIs & Services tab.

  2. Click Credentials.
  3. On the Credentials tab, click Manage Service Accounts available at the bottom right corner.

    The Service Accounts window is displayed.

  4. Click + CREATE SERVICE ACCOUNT.

    Create service account window is displayed.

  5. Enter the name of the service account in Service account name text field.

  6. Select Owner as the Role from the drop-down menu.
  7. 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.

  8. Click Create.

To select and authorize the API scopes

  1. Login to the G Suite admin console with your domain.

  2. On the Admin console home page, click Security.

  3. Click Advanced settings.

  4. Click Managed API client access.

  5. Enter the client name and the description in the Name and Description text field respectively.

  6. Enter the email in the Email text field.

  7. 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

  8. After adding the API scoes, click Authorize.

    The unique Id and the scopes added is displayed.

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

  1. Login to the Salesforce developer edition link: https://developer.salesforce.com/signup?d=70130000000td6N.

  2. Provide the relevant details and click Sign me up.

    A trail account is created and an instance is assigned.

  3. Switch the view to Saleforce classic view by clicking Switch to Salesforce Classic.
  4. Click the Setup tab.
  5. Click Build | Create | Apps.
  6. In the Connected Apps section, click New.
  7. In the Basic Information section, enter the relevant details.
  8. In the API (Enable OAuth Settings) section, select Enable OAuth Settings checkbox.
  9. Provide the https://app.getpostman.com/oauth2/callback URL in the Callback URL text field.
  10. From the Selected OAuth Scopes drop-down menu, select Full Access (full).
  11. Click Save.
  12. 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.

  1. On the home page, click My Settings.

  2. Click Personal | Reset My Security Token.
  3. Review the information displayed on the screen and click Reset Security Token.
  4. Provide the relevant information such as:

IMPORTANT:

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

  1. Login to the Microsoft Azure portal and select Azure Active Directory from FAVORITES.

  2. From Manage section, select App Registrations (Preview).
  3. Click New registration and provide the necessary details.
  4. Select the created application and click View API Permissions.
  5. 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.

  6. Click Grant admin consent for Default Directory checkbox to grant necessary permissions.
  7. From the created application, click App Registrations (Preview) and note the Application (client) ID and Directory (tenant) ID.
  8. Select Certificates & secrets and click New client secret to generate the secret.
  9. 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.
  10. Click Accept.

Providing permission to update or delete users password

  1. Install the Azure AD PowerShell v1 module (MSOnline).

  2. Connect to your Azure AD B2C tenant.

  3. 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:

Generating a private key for service account in GoToMeeting

A private key has to be generated to access the GoToMeeting service account.

Generating a private key

  1. Create an account in GoToMeeting.

  2. Login to the GoTo Developer Center. For more information use the link here: https://goto-developer.logmeininc.com/.
  3. Click MyApp and create an application. Note the Consumer key and Consumer secret.
  4. Login to the GoToMeeting administrator portal to find the admin key in the URL.
Documentos relacionados