As far as I know, I used external vidm components.
I guess that my experience could help your comprehension.
As you understood, user management is realized exclusively through vidm.
You are able to use an existing vidm or deploy a new one.
I used the first option :
-> Deployed vidm first
-> Prepare vidm : Database / Certificates (2 instance with load balancer if possible)
-> With lifecycle I choose to use existing vidm and then define directory parameters -> that will be add to the existing vidm.
My first experience to defined directory first on vidm and just specify the vidm I used but I encountered some error.
But with VMware SDDC stack, I defintely prefered to define specific vidm and with pointing automaticaly or not vRA, vRLI, vROPs, vRNI on this dedicated authentication solution.
I am getting the same issue, trying to add vRA 7.3.1 vIDM to VRLCM 2.0 and i am getting organization not found.
It might be referring to a problem with the 'hostname' field of the vIDM deployment.
See my blog post for details: Some notes on the -hostname- field, when installing #vIDM with #vRSLCM – The Fluffy Admin
I have a vRA 7.3.1 instance that we use as the vIDM for all our vIDM supported products. Id like to use this vIDM for vRLCM as well. On the user management page i put in the Active Directory information that includes the service account that we use to do user binds and the OUs that contain all the users and groups we want to use with vRLCM. I then specify the vIDM hostname as the FQDN of the load balancer VIP for my production vRA environment and ive tried a slew of UN/PW combos for administrator, firstname.lastname@example.org, domain joined service accounts, etc with none of them working. I continually get the error "com.vmware.vrealize.lcm.common.exception.LcmException: Failed to get admin token: Organization not found." error. I'm not sure if this is an LDAP error or an issue with my vIDM. I'm honestly not sure what version of vIDM vRA 7.3 includes so that could be an issue too. Anyone out there get this to work? Anyone see this error and work around it?