My previous comment - https://experienceleaguecommunities.adobe.com/t5/workfront-events/workfront-coffee-break-wednesday-may-29th-at-8am-pt-best/ec-p/676478/highlight/true#M302

Similiar to WF with non SSO users they will need to be manually added to the AC and assigned to the WF product. They will be setup as an Adobe ID instead of a federated which will allow them to use a Username/Password to authenticate into the console and gain access to WF.

Your migration specialist can migrate users from WF into that Admin Console. You will just want to let them know you want to do that and for which environments.Users do have to be added to the WF environment inside of the console before they can access WF. If you are looking for a way to automate th...

The WF SSO configuration will be going away and the AC SSO config will be the new way authentication is handled. You will want to setup that configuration to work with your orginizational needs. You can have more than one SSO configuration in the console but you can only have 1 configuration per cla...

You can still add users to WF through the API. When this is done the user needs a System Admin approval before they can be activated in WF and pushed to the AC.You can also use the Admin Consoles UMAPI functionality to add users to the AC and assign the WF product. This does not require system admin...

The username/password authenitcation only applies to WF modules. Existing connections will continue to work however, when setting up new connections you will not be able to authenticate with a WF username/password.If you need to setup a new connection I recommend logging into WF first as the user yo...

If you are seeing a discrepancy between WF active users and the Admin Console assigned users please submit a support case so we can investigate further. There are a variety of things that can cause this to occur so a support agent will need to access your console and WF. If you have some users who a...