Atlassian IAM
Atlassian IAM Pack.#
This Integration is part of theSupported versions
Supported Cortex XSOAR versions: 6.0.0 and later.
Note: This integration should be used as part of our IAM premium pack. For further details, visit our IAM pack documentation. For more information, please refer to the Identity Lifecycle Management article. Integrate with Atlassian's services to execute generic ILM management operations such as create, update, delete, etc, for employee lifecycle processes.
#
Configure Atlassian IAM on Cortex XSOARNavigate to Settings > Integrations > Servers & Services.
Search for Atlassian IAM.
Click Add instance to create and configure a new integration instance.
Parameter Description Required Atlassian URL True Access Token True Directory ID True Trust any certificate (not secure) False Use system proxy settings False create_user_enabled Allow creating users. If set to false, iam-create-user command will be skipped, and user will not be created. False update_user_enabled Allow updating users False enable_user_enabled Allow enabling users False disable_user_enabled Allow disabling users False Automatically create user if not found in update command False Incoming Mapper Incoming Mapper True Outgoing Mapper Outgoing Mapper True - To allow the integration to access the mapper from within the code, as required by the ILM pack, both mappers have to be configured in their proper respective fields and not in the "Mapper (outgoing)" dropdown list selector.
- Click Test to validate the URLs, token, and connection.
#
CommandsYou can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
#
iam-create-userCreates a user.
#
Base Commandiam-create-user
#
InputArgument Name | Description | Required |
---|---|---|
user-profile | User Profile indicator details. | Required |
allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
IAM.Vendor.brand | String | Name of the integration. |
IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
IAM.Vendor.email | String | The employee's email address. |
IAM.Vendor.errorCode | Number | HTTP error response code. |
IAM.Vendor.errorMessage | String | Reason why the API failed. |
IAM.Vendor.id | String | The employee's user ID in the app. |
IAM.Vendor.instanceName | string | Name of the integration instance. |
IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
IAM.Vendor.username | String | The employee's username in the app. |
#
Command Example!iam-create-user user-profile=`{"emails":[{"value":"testatlas@paloaltonetworks.com","type":"work","primary":"true"}],"is_active": "true", "userName":"testatlas@paloaltonetworks.com"}` using="Atlassian IAM_instance_1"
#
Context Example#
Human Readable Output#
Create User Results (Atlassian IAM)
brand instanceName success active id username details Atlassian IAM Atlassian IAM_instance_1 true true 247b915a-9d6c-4cd5-b5a5-071b1b3abc2e testatlas@paloaltonetworks.com schemas: urn:scim:schemas:extension:atlassian-external:1.0,
urn:ietf:params:scim:schemas:core:2.0:User,
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User
userName: testatlas@paloaltonetworks.com
emails: {'value': 'testatlas@paloaltonetworks.com', 'type': 'work', 'primary': True}
meta: {"resourceType": "User", "location": "https://api.atlassian.com/scim/directory/315e79ae-404a-4061-8a88-df91c8c7db34/Users/247b915a-9d6c-4cd5-b5a5-071b1b3abc2e", "lastModified": "2021-02-16T15:05:41.185473Z", "created": "2021-02-16T15:05:41.185473Z"}
groups:
urn:scim:schemas:extension:atlassian-external:1.0: {"atlassianAccountId": "602bdf457b23f40068547c25"}
id: 247b915a-9d6c-4cd5-b5a5-071b1b3abc2e
active: true
#
iam-update-userUpdates an existing user with the data passed in the user-profile argument.
#
Base Commandiam-update-user
#
InputArgument Name | Description | Required |
---|---|---|
user-profile | A User Profile indicator. | Required |
allow-enable | When set to true, after the command execution the status of the user in the 3rd-party integration will be active. Possible values are: true, false. Default is true. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
IAM.Vendor.brand | String | Name of the integration. |
IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
IAM.Vendor.email | String | The employee's email address. |
IAM.Vendor.errorCode | Number | HTTP error response code. |
IAM.Vendor.errorMessage | String | Reason why the API failed. |
IAM.Vendor.id | String | The employee's user ID in the app. |
IAM.Vendor.instanceName | string | Name of the integration instance. |
IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
IAM.Vendor.username | String | The employee's username in the app. |
#
Command Example!iam-update-user user-profile=`{"email": "testatlas@paloaltonetworks.com", "username": "testatlas@paloaltonetworks.com", "title": "Manager"}` using="Atlassian IAM_instance_1"
#
Context Example#
Human Readable Output#
Update User Results (Atlassian IAM)
brand instanceName success active id username details Atlassian IAM Atlassian IAM_instance_1 true true 247b915a-9d6c-4cd5-b5a5-071b1b3abc2e testatlas@paloaltonetworks.com testatlas@paloaltonetworks.com schemas: urn:scim:schemas:extension:atlassian-external:1.0,
urn:ietf:params:scim:schemas:core:2.0:User,
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User
userName: testatlas@paloaltonetworks.com
emails: {'value': 'testatlas@paloaltonetworks.com', 'type': 'work', 'primary': True}
meta: {"resourceType": "User", "location": "https://api.atlassian.com/scim/directory/315e79ae-404a-4061-8a88-df91c8c7db34/Users/247b915a-9d6c-4cd5-b5a5-071b1b3abc2e", "lastModified": "2021-02-16T15:05:41.185473Z", "created": "2021-02-16T15:05:41.185473Z"}
groups:
urn:scim:schemas:extension:atlassian-external:1.0: {"atlassianAccountId": "602bdf457b23f40068547c25"}
id: 247b915a-9d6c-4cd5-b5a5-071b1b3abc2e
active: true
#
iam-get-userRetrieves a single user resource.
#
Base Commandiam-get-user
#
InputArgument Name | Description | Required |
---|---|---|
user-profile | A User Profile indicator. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
IAM.Vendor.brand | String | Name of the integration. |
IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
IAM.Vendor.email | String | The employee's email address. |
IAM.Vendor.errorCode | Number | HTTP error response code. |
IAM.Vendor.errorMessage | String | Reason why the API failed. |
IAM.Vendor.id | String | The employee's user ID in the app. |
IAM.Vendor.instanceName | string | Name of the integration instance. |
IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
IAM.Vendor.username | String | The employee's username in the app. |
#
Command Example!iam-get-user user-profile=`{"email": "test@paloaltonetworks.com", "username": "testDemisto"}` using="Atlassian IAM_instance_1"
#
Context Example#
Human Readable Output#
Get User Results (Atlassian IAM)
brand instanceName success id username details Atlassian IAM Atlassian IAM_instance_1 true 550364dd-1c1e-4953-bffc-418fce013c2e testDemisto schemas: urn:scim:schemas:extension:atlassian-external:1.0,
urn:ietf:params:scim:schemas:core:2.0:User,
urn:ietf:params:scim:schemas:extension:enterprise:2.0:User
userName: testDemisto
emails: {'value': 'test@paloaltonetworks.com', 'type': 'work', 'primary': True}
title: Team Lead
meta: {"resourceType": "User", "location": "https://api.atlassian.com/scim/directory/315e79ae-404a-4061-8a88-df91c8c7db34/Users/550364dd-1c1e-4953-bffc-418fce013c2e", "lastModified": "2021-02-15T17:01:01.876067Z", "created": "2021-02-15T13:26:34.13545Z"}
groups:
urn:scim:schemas:extension:atlassian-external:1.0: {"atlassianAccountId": "5f3589458d89e30046317d34"}
id: 550364dd-1c1e-4953-bffc-418fce013c2e
#
iam-disable-userDisable an active user.
#
Base Commandiam-disable-user
#
InputArgument Name | Description | Required |
---|---|---|
user-profile | A User Profile indicator. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
IAM.Vendor.active | Boolean | When true, indicates that the employee's status is active in the 3rd-party integration. |
IAM.Vendor.brand | String | Name of the integration. |
IAM.Vendor.details | string | Provides the raw data from the 3rd-party integration. |
IAM.Vendor.email | String | The employee's email address. |
IAM.Vendor.errorCode | Number | HTTP error response code. |
IAM.Vendor.errorMessage | String | Reason why the API failed. |
IAM.Vendor.id | String | The employee's user ID in the app. |
IAM.Vendor.instanceName | string | Name of the integration instance. |
IAM.Vendor.success | Boolean | When true, indicates that the command was executed successfully. |
IAM.Vendor.username | String | The employee's username in the app. |
#
Command Example!iam-disable-user user-profile=`{"email": "testdemisto@paloaltonetworks.com", "username": "Demisto"}` using="Atlassian IAM_instance_1"
#
Context Example#
Human Readable Output#
Disable User Results (Atlassian IAM)
brand instanceName skipped reason Atlassian IAM Atlassian IAM_instance_1 true User does not exist