Create User Accounts via the Workfront API

With workfront API, provide an option to activate users up on creation via the workfront API's. Currently users are created in a "deactivated" state and requires manual action to activate.

Why is this feature important to you: We have an automated user provisioning workflow in place and the above limitation is causing a holdup requiring a human intervention to activate user account.

Expected behaviour: Workfront user creation API's should be able to create the user account that in an activated status. Either the  user create API should be updated or provide separate Workfront API to activate the user.

Hi all,

We finally got this working. It's not as pretty as before. I create the account in Workfront using the original code I had.

I then use the API to create the account in Adobe Admin Console via that API. It then seems to setup correctly and the user no longer needs approving. 

I've had one report that the account still needed activating, but it generally seems to work. 

Hopefully one day they will fix it so we don't need the 2nd step. But I'm not holding my breath 😉

Regards,

Rob

@robertdy I really appreciate your reply. Thanks for giving us an update.

@bfan

It's very frustrating. Some people seem to think the old creation method should work if the API user is a product admin, others think it will never work. All I know is I'm every admin possible and it still doesn't work.

Adobe User Management API is still not working, they are still "gathering information" with no ETA on a fix.

@brmorril I think you made the right decision. The change management was too much for us to roll it back. I will let you know when we get it working 🙂

Rob

We ended up rolling back our production instance off of IMS about 2 weeks ago until Adobe addresses this issue later in Q1FY24.  Until then, we are now back to normal in production but have IMS enabled in Preview and Sandbox so we can continue testing in those environments when the problem is "fixed".

I wanted to bump this thread to see if there was any progress. Migrating to ABM broke our ability to auto-provision users. We started looking at using the API to replicate this functionality, but reading this thread makes it seem like we need a workaround for the workaround. 

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.

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 🙂

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.

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."