Page Comparison

Feature

Description

User Account Provisioning

You can use our Azure AD connector to create user accounts automatically. See this video for more information:

Azure Provisioning Apps and Groups

Watch this video to see how you can use the Azure AD connector to automatically provision apps and groups to your users:

Security and Compliance

This video provides information on security and compliance when using OnLink with Azure AD

Create User

Set the required fields when calling Create User function using the post function screen:

You can also use KeyValue pair to add any string, date or boolean attributes as supported by Azure AD, including custom attributes. See their list here.

map:birthday=customfield_10122
map:city=customfield_10123
map:department=customfield_10124
map:employeeHireDate=customfield_10125
map:employeeType=customfield_10126
map:officeLocation=customfield_10127
map:userType=customfield_10128
map:manager=customfield_10129 #can be user picklist or text with email value

When using the “Create User” function, you can set the “Password” field to a temporary password. You can either set this to a static value or combine the static value with a dynamic prefix to generate a unique password for every user created.

You can use this smart value in the Password field: {dynamic_prefix}

This generates an alpha-numeric string of length 20. This may not, by itself, meet your password restrictions. So, we recommend setting the Password field to something like this:

{dynamic_prefix}Me3t$PwdReqs!!

The dynamic part will ensure that the password is unique and the “Me3t$PwdReqs!!” is a string that meets your organization’s password requirements.

Note that, this unique password can then be sent via email using OnLink’s Email connector. See this for more information.

The dynamic prefix is generated using the issue key (the issue on which the post function executes). So you’ll need to make sure that the Create User and Email functions are executed on the same issue.

Assigning Licenses

OnLink supports assigning licenses to users as part of the Create User function. An admin can select allowed Licenses in the Connections screen (#1 below). Then users can set the "OnLink Azure Licenses" customfield in a Jira issue assign licenses (#2 below).

Image Added