Atlassian Suite Cloud - Create User Issue

Today we started getting an error when trying to create a new user in Atlassian Suite Cloud using the VA Based Connector.

openconnector.ConnectorException: {"errorMessages":["You must specify the products that user can access."],"errors":{}}

We have been using this source for over 18 months and have never seen this error. We were able to create accounts a few days ago. The API documentation from Atlassian (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-rest-api-3-user-post) shows that products is a required field, but the Sailpoint Connector document doesn’t mention it. Not sure if this is a newly required field by Atlassian, or if there is something wrong with the Sailpoint Connector. We have opened a support case.

Has anyone run into this issue?

We are gettting the same error. I too have opened a support case.

We are also getting this error.

We also started this error.
Please let me know if you got any solution.

I have received response from our Atlassian Team. “products” field is mandatory now as part of Create User API.

I have tried through Postman, it worked after adding blank products as below:
“products”:

But can someone suggest, how can we add blank array value in any field through IdentityNow?

You try creating user using postman with same fields and check if you get the error.In that case you need to add the additional field in create profile.

Thanks
Shantanu

I have tried adding the field to the Create profile. Unfortunately I have been unable to get it working as ISC will exclude the field if it is blank. Anyone have any guidance on how to pass a blank array in the Create profile?

We heard back from Support and Engineering. The Atlassian connector has been changed to fix the Create Account function. Sandbox tenants were updated on May 28th, production tenants are being updated on May 30th (today).

I have confirmed in our tenants that the Create Account function has been fixed, and users are being created normally again.

We hadn’t seen this error previously, but since 6/6, we have seen this occur 4 times in our Prod, most recently today. I opened a support ticket, just wanted to mention it in case anybody else is still seeing this error.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.