What are the endpoints used by Atlassian Suite - Cloud connector for the integration? We are facing some issue during the account creation (displayName is not populated properly even after sending it the right way). So, wanted to understand if we can create user outside of the SailPoint and see how that behaves. Please share the documentation link if possible.
This question is based on this topic: Create Account / Provisioning Policy
@nadhikari_identitynow Can you Expand on what you have configured so far to help populate the value? You mention that you are “sending it the right way”, but there still might be a step missing from that. The more information you can provide, the better for assistance.
I would also consider configuring the connector for logging, and reviewing what is being sent to the service: Enable Connector Logging
If you can get a log that shows the provisioning plan, you can verify that the value is in the plan and what field it is trying to set.
Are the other fields being set correctly?
Hi @gmilunich,
Thank you for your response. We are setting the Create Account profile as: ```
{
“name”: “Create Account”,
“description”: null,
“usageType”: “CREATE”,
“fields”: [
{
“name”: “emailAddress”,
“transform”: {
“type”: “identityAttribute”,
“attributes”: {
“name”: “email”
}
},
“attributes”: {
“cloudRequired”: “true”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
},
{
“name”: “displayName”,
“transform”: {
“type”: “concat”,
“attributes”: {
“values”: [
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “FIRST_NAME”
},
“type”: “accountAttribute”
},
" ",
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “LAST_NAME”
},
“type”: “accountAttribute”
}
]
}
},
“attributes”: {
“cloudRequired”: “true”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
},
{
“name”: “fullName”,
“transform”: {
“type”: “concat”,
“attributes”: {
“values”: [
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “FIRST_NAME”
},
“type”: “accountAttribute”
},
" ",
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “LAST_NAME”
},
“type”: “accountAttribute”
}
]
}
},
“attributes”: {
“cloudRequired”: “true”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
},
{
“name”: “name”,
“transform”: {
“type”: “concat”,
“attributes”: {
“values”: [
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “FIRST_NAME”
},
“type”: “accountAttribute”
},
" ",
{
“attributes”: {
“sourceName”: “Workday Preview”,
“attributeName”: “LAST_NAME”
},
“type”: “accountAttribute”
}
]
}
},
“attributes”: {
“cloudRequired”: “true”
},
“isRequired”: false,
“type”: “string”,
“isMultiValued”: false
}
]
}``
To trigger a create account, we are trying to assign a role via request center which has confluence-user group as entitlement.
In the account activity logs, it shows we are passing all the attributes we set accurately.
The ccg debug logs also shows the values are passed as expected:
<!DOCTYPE ProvisioningPlan PUBLIC \"sailpoint.dtd\" \"sailpoint.dtd\">
<ProvisioningPlan nativeIdentity=\"<Removed>\">
<AccountRequest application=\"Confluence [source]\" op=\"Create\">
<AttributeRequest name=\"groups\" op=\"Add\" value=\"confluence-users\"\/>
<AttributeRequest name=\"emailAddress\" op=\"Add\" value=\"[email protected]\"\/>
<AttributeRequest name=\"displayName\" op=\"Add\" value=\"John Doe\"\/>
<AttributeRequest name=\"fullName\" op=\"Add\" value=\"John Doe\"\/>
<AttributeRequest name=\"name\" op=\"Add\" value=\"John Doe\"\/>
<ProvisioningResult status=\"committed\"\/>
<\/AccountRequest>
<Attributes>
<Map>
<entry key=\"accessRequestType\" value=\"GRANT_ACCESS\"\/>
<entry key=\"identityRequestId\" value=\"sdd979a71ca8934120ab174100993625e7\"\/>
<entry key=\"requester\" value=\"<removed>\"\/>
<entry key=\"source\" value=\"LCM\"\/>
<\/Map>
<\/Attributes>
<\/ProvisioningPlan>
However, the Full name field in the target system doesn’t reflect what we are passing.
The full name is JDoe instead of John Doe.
The reason I am trying to get the connector details on what API are being used so that we can figure out what is the exact attribute it is expecting in the Full name field.
Any help would be highly appreciated.
Thank you again!
-Nischal
Ok, for clarification and to make sure I understand correctly, with that provisioning plan that was sent in, with both fullName and displayName set to “John Doe”, when you check the system, the full name there is set to “JDoe”, is that correct?
I don’t have access to Atlassian, so I may not be able to help further, but I can try.
Hi @gmilunich ,
Thank you for the response.
That is correct. Our ccg debug log shows it is passed and the user is created. But, when we look at the Atlassian side, the Full name field is JDoe instead of John Doe.
Thank you for looking into this.
Thanks,
Nischal