Unfortunately there isn’t any official supported way to Automate PSC AD Integrated identity source in VCSA 6.5u1, u2 or 6.7u1
In the past in v5.5 / 6.0 or 6.5 that was possible using sso-add-native-ad-idp.sh and sso_import.sh however for some reason those utilities are no longer present in 6.5u1,u2 or 6.7u1 image.
For VCSA 5.5 PSC AD integrated identity source automation example using those files https://www.virtuallyghetto.com/2015/01/automating-active-directory-identity-source-default-domain-in-vsphere-web-client.html
Major pain point for any pod / stack build relying on orchestration! No identity source, prevents from importing users and groups and so on.
The workaround is to spin up VCSA 6.5 GA or earlier and extract:
Once done import into newly deployed PSC/VCSA (as a part of the workflow)
Syntax I’m using to built this part into Jenkins orchestration, (PSC is already joined to domain using /opt/likewise/bin/domainjoin-cli)
#obtain the files
$domain = <your domain>
$repo = <your http repo>
chmod +x ./sso-add-native-ad-idp.sh
chmod +x ./sso_import.sh
#Move the script to DIR it expects
cp sso_import.sh /usr/lib/vmidentity/tools/scripts/."
#set identity source
It throws an error after Identity source configuration but it works!!
I can use my domain creds, I can also remove this identity source using Web Client and re-add it so no stable objects there.
hopefully that help you folks
If someone found other ways to automate it please let me know!