<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00007HEdGaSALOkta Classic EngineSingle Sign-OnAnswered2026-04-01T09:00:20.000Z2019-12-10T23:36:03.000Z2020-01-07T00:13:44.000Z

oi8ak (oi8ak) asked a question.

Error when attempting to provision a sas application 'Workramp'

Error occurred will assigning this app.

 

Automatic provisioning of user xxxxx to app Workramp failed. Error while creating user xxxxx@xxxxx: Conflict. Errors reported by remote server. Duplicate resource


  • t529b (t529b)

    It sounds like the user account that Okta is trying to provision in Workramp already exists. And the conflicting account may not be in your instance of Workramp. Maybe the user in question created their own account independently, outside of your instance, but Workramp enforces unique account usernames globally.

     

    We encounter this a LOT with LucidChart. Some users create "free", standalone LucidChart accounts to try out the service, and then when we attempt to onboard them into our corporate instance, LucidChart rejects the provisioning attempt because the user created their account using their corporate email address. Then I have to contact the user and get them to rename or delete the account that is interfering with provisioning, then have Okta retry the provisioning.

    Expand Post
    Selected as Best
  • t529b (t529b)

    It sounds like the user account that Okta is trying to provision in Workramp already exists. And the conflicting account may not be in your instance of Workramp. Maybe the user in question created their own account independently, outside of your instance, but Workramp enforces unique account usernames globally.

     

    We encounter this a LOT with LucidChart. Some users create "free", standalone LucidChart accounts to try out the service, and then when we attempt to onboard them into our corporate instance, LucidChart rejects the provisioning attempt because the user created their account using their corporate email address. Then I have to contact the user and get them to rename or delete the account that is interfering with provisioning, then have Okta retry the provisioning.

    Expand Post
    Selected as Best
This question is closed.
Loading
Error when attempting to provision a sas application 'Workramp'