.png?sv=2022-11-02&ss=b&srt=o&spr=https&st=2024-04-29T16%3A06%3A51Z&se=2024-04-29T16%3A16%3A51Z&sp=r&sig=RoBDVuGA1Ce3ukfUsHasQExxbMUMHZlVahkcVlOpL9A%3D){kind=logo}
Jira Software - Create User
- 15 Jan 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Jira Software - Create User
- Updated on 15 Jan 2024
- 2 Minutes to read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Jira Software - Create User creates a user in Atlassian (formerly Jira Software) for each asset that matches the parameters of the selected saved query, and the other Enforcement Action settings or the assets selected on the relevant asset page.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
- Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
- Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from Atlassian (formerly Jira Software) adapter - Select this option to use the Atlassian adapter credentials.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Required Fields
These fields are required to run the Enforcement Action.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
- Use IFTTT generated email - Select this option to generate users from a statement in the Dynamic Values field when their 'email' field is not populated in Jira. For more information see Creating Enforcement Action Dynamic Value Statements.
Connection Parameters
If Use stored credentials from the Atlassian (formerly Jira Software) adapter is disabled, these fields are required:
- Jira API Version (required, default: V3) - Select your Jira API version.
- Atlassian Admin API - Organization ID and Atlassian Admin API - API key - The organization ID and an organization API key generated for fetching SaaS data. Needed for fetching organizational data.
- Password - The password for the Atlassian user account. Needed for fetching Settings from Atlassian.
- 2FA Secret Key - If you access Atlassian through an SSO solution that requires two-factor authentication, and you want to fetch Settings from Atlassian, you will need to generate a secret key in that solution and paste it here. See instructions for performing this action in Okta.
Gateway Name - Select the gateway through which to connect to perform the action.
Use the scheduling options to execute Enforcement Actions on specific dates and times. You can also configure repeat schedules.
For more details, see Scheduling Enforcement Set Runs.
APIs
Axonius uses the Jira Cloud Platform REST API.
Permissions
The credentials used to connect to Atlassian must have the permissions needed to create users in Atlassian.
For more details about other Enforcement Actions available, see Action Library.
Was this article helpful?