Create User Accounts via the Workfront API

[#1]

Description - Before the upgrade to the Adobe Admin Console, we could create users via the API. It now creates them in a pending approval state and we have to manually approve them. 

Why is this feature important to you - This is causing a bottleneck in quickly on-boarding users to Workfront.

How would you like the feature to work - I'd like it to work as it did before :), or allow an option to be set to pre-approve the users. Or even a separate API call to approve the user.

Current Behaviour - Account is created, but requires manual approval, once approved the account is made in the Adobe Admin Console.

[#2]

100% agree with this.  We use an external webform for users to submit requests and if they don't exist in Workront already, the automation creates the user prior to submitting the request.  This entire process is now broken after migrating to Admin Console and is causing major issues company-wide since we have multiple webforms in use by many teams.  If we could include the approval step in the automation, that would be fine, or have a setting that doesn't require the approval would also help.  Somehow we need this resolved.  Come on Adobe, help us move forward, not backward!

[#3]

Is the API pointing to Workfront to create the user? If so, when we asked our Technical Support Engineer helping us to plan our migration to the Adobe Admin Console about this subject, we were told, "if you were running that automation with a System Admin user in Workfront, you shouldn't run into any issues, but that would also require it to be a System or Product Admin inside of the Admin Console that same user." 

[#4]

We made sure our API user is a Product Profile Admin for Workfront within Admin Console.  We even tested with a regular Sys Admin's API key and ran into the same issue, though both users can successfully create users within the Workfront UI without having to approve the new user.  This has become such a huge pain point that we are contemplating having IMS turned back off until the issue can be resolved by Adobe.

[#5]

Yes,

We are pointing to Workfront to create the user. The account we use for the API is definitely a system administrator. 
Definitely a massive pain that really needs resolving ASAP.

Rob

[#6]

@LaurenWood 

I should add, we raised a support ticket and they said:

"I can confirm that I have been unable to figure out a way to create the account via the API script. I agree that there does not appear to be any documentation that supports your request. Therefore, you are advised to approve the account without using the API. However, if you feel this would improve your ability to work effectively within our software, I would suggest submitting this idea to get it reviewed by our development team"

This doesn't seem to match what your migration team is saying

Rob

[#7]

I've asked for clarity here and also upvoted the idea. This is unsettling and could be show stopper for migrations. Thanks for sharing your experience.

[#8]

Here is what I heard back today:

"If you add a user to Workfront via the API, you do not have an Admin Console authentication token. This means that the user cannot be created into Admin Console, instead an approval is created and must be approved from the UI. If you attempt to approve the user via the API, you still do not have an Admin Console token and this will not create the user in the Admin Console. You must use the UI to approve the user creation.

This means that you can create users with the API you just need to approve them inside of Workfront.

API functionality to change this in the future is being looked into but there are no commit dates for that enhancement at this time."

[#9]

To add on to this, we were provided a conceptual workaround (nothing has been tested by Adobe yet - it's all theoretical) to use the UMAPI (User Management API) to handle users on the IMS side instead of WF side.  However, we would need to grab the Access Token from IMS and send it with the Workfront calls.  That opens up additional challenges as it would require an integration with a different IMS app to get the token. 

They did let us know that fixing the API is on the roadmap, but not until Q1FY24 or later.

We are currently looking at rolling our production instance back off of IMS while keeping our lower environments on IMS until this issue is fully resolved.

[#10]

Hi, 

Yes, this manual approval was what we experience with our API. 

I developed the script to create through UMAPI. This created the user in the Admin Console, but the user in Workfront was not created. However, we assign our product access via groups in the Admin console and they think this might be the issue. So I'm going to investigate further today. I'll let you know how I get on

[#11]

Still not joy with creating the account the the UMAPI. I have a support ticket open.

The account is created OK in the Adobe Admin Console, but the account doesn't appear in Workfront then.

We will continue battling with this.