Earlier this year my customer would get an CSP migration e-mail regarding the connector based deployment scenario would be deprecated moving forward with VMware/Broadcom and the latter acquiring VMware. This is regarding https://docs.vmware.com/en/VMware-Cloud-services/services/setting-up-enterprise-federation-cloud-services/GUID-76FAECB3-CFAA-461E-B9C9-2A49C39CD17F.html
After some discussion and support case feedback around this and explaining that connector less isn’t a valid option for our use case with Workspace ONE (now Omnissa) and many question marks around that one it finally became clear it’s two seperate things now and the solution would be:
* Current CSP federation with VMware in the IDP/SP portion supports SCIM/JIT and the application registration needs to be cloned/updated for that with Broadcom
* Current CSP federation with Omnissa (old VMware EUC) needs to be edited to still use the current Enterprise Federation for Omnissa
Bottomline is that VMware/Broadcom don’t support the connector anymore and have moved on to a builtin setup for that and Omnissa still leverages the AWS / Broker solution with a Access in between for the authentication brokering part and synchronisation will still work on the connector based solution not impacting anything.
Hope it helps.