Atlassian Cloud
Atlassian cloud lets you automate user provisioning from your identity provider to Atlassian Cloud thus ensuring a smooth provisioning/de-provisioning users and groups from an identity provider to Confluence and Jira Cloud. With this, you can write your own integration with an external identity provider using the SCIM 2.0 protocol to manage your Atlassian Cloud users and groups.
Supervisor configuration parameters
To configure the connector, the following parameters are required:
Supported objects and operations
Users
Table 430: Supported operations for Users
Create User |
POST |
Update User |
PUT |
Get User by id |
GET |
List User |
GET |
Delete User |
DELETE |
Groups
Table 431: Supported operations for Groups
Create Group |
POST |
Update Group |
PUT |
Get Group by Id |
GET |
List Groups |
GET |
Delete Group |
DELETE |
Mandatory fields
Users
-
userName
-
emails[].value
-
emails[].primary = true
Groups
User mapping
The user and group mappings are listed in the tables below.
Table 432: User mapping
id |
id |
userName |
userName |
name.formatted |
name.formatted |
name.givenName |
name.givenName |
name.familyName |
name.familyName |
name.middleName |
name.middleName |
name.honorificSuffix |
name.honorificSuffix |
name.honorificPrefix |
name.honorificPrefix |
emails[].value |
emails[].value |
emails[].type |
emails[].type |
emails[].primary |
emails[].primary |
phoneNumbers[].value |
phoneNumbers[].value |
phoneNumbers[].type |
phoneNumbers[].type |
phoneNumbers[].primary |
phoneNumbers[].primary |
active |
active |
externalId |
externalId |
timezone |
timezone |
title |
title |
preferredLanguage |
preferredLanguage |
nickname |
nickName |
displayName |
displayName |
enterpriseExtension.organization |
enterpriseExtension.organization |
enterpriseExtension.department |
enterpriseExtension.department |
atlassianExtension.atlassianAccountId |
enterpriseExtension.atlassianAccountId |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
Groups
Table 433: Group mapping
id |
id |
displayName |
displayName |
externalId |
externalId |
members[].value |
members[].value |
members[].type |
members[].type |
members[].display |
members[].display |
meta.created |
meta.created |
meta.lastModified |
meta.lastModified |
Connector limitations
Appendix: Creating a service account in Google Workspace
Creating a service account in Google Workspace
You must obtain a JSON file with Private Key to authorize the APIs to access data on Google Workspace 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 Google workspace 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
-
https://www.googleapis.com/auth/admin.directory.group.member
-
https://www.googleapis.com/auth/admin.directory.domain
-
https://www.googleapis.com/auth/admin.directory.domain.readonly
-
https://www.googleapis.com/auth/admin.directory.rolemanagement
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.
Appendix: Setting a trial account on Salesforce
Setting a trial account on Salesforce
To login to the Saleforce application, you must create a trial 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 trial 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 url text https://app.getpostman.com/oauth2/callback in the Callback URL text field.
NOTE: This url must be used just to configure the trial account and not as a browsing link.
- From the Selected OAuth Scopes drop-down menu, select Access and manage your data(api).
- 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:
Registering the application, providing necessary permissions, retrieving Client Id and Client Secret from the Azure AD tenant
Registering the application, providing necessary permissions, retrieving Client Id and Client Secret from the Azure AD tenant
This section provides the details about registering the application, providing necessary permissions, retrieving Client Id and Client Secret from the Azure AD tenant, for both single tenant and multi-tenant connector configuration.
NOTE: Safeguard for Privileged Passwords only allows for a single tenant connector configuration..
To register application, provide appropriate permissions, retrieve client ID, and client secret from the Azure AD tenant
-
Login to Azure portal and select Azure Active Directory.
-
Select App registrations.
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:
- Application name
- Redirect URL: https://connect-supervisor.cloud.oneidentity.com/v1/consent.
- Select the created application and click View API Permissions.
- From API permission, add the required permissions for Microsoft Graph API (delegated and application permissions).
The registered application must have the following permissions:
- Directory.ReadWrite.All
- Group.ReadWrite.All
- User.ManageIdentities. All
- User.ReadWrite.All
-
Create a user under Azure Active Directory and assign Privileged role administrator role under the user's Assigned roles.
NOTE: A Global administrator would also be able to provide consent.
-
For the Azure Active Directory, assign User administrator role for the application created.
NOTE: For Safeguard for Privileged Passwords, you must assign at least the Helpdesk Administrator role for the application created, but should assign a higher role if you want to manage special accounts (for example, Billing Administrator or Global Administrator).
To assign User administrator role for the application created:
- Select Roles and administrators.
-
Click + Add Assignments, and search the name of the application created.
- Gather the following details from the corresponding pages of the application given in the table below.
Table 434: Application details
Details |
Page |
Application (client) ID
Azure Active Directory's Directory (tenant) ID |
Overview |
Client Secret |
Certificates & secrets |
More details on Azure AD
For more details on Azure AD, refer the following links: