In this blog post, we will now deploy an instance of VMware Private AI Services (PAIS) that will use the Vector Database that was provisioned earlier and the OIDC Client Application that we had also setup earlier using the Authentik Identity Provider (IdP).
Requirements:
As part of VMware Cloud Foundation (VCF) 9.0, users can now enable the new VCF Single Sign-On (SSO) capability, allowing true single sign-on across all components within the VCF solution. While modern IdPs such as Okta, PingFederate, Microsoft Entra ID and Microsoft ADFS continue to be supported for Production deployments, users might want to play with the new VCF SSO capability within their lab environment that may not have external access or you may want to use an IdP that is self-hosted for learning purposes.
In addition to the IdPs listed above, you can also play with the new VCF SSO using a generic OIDC provider. Keycloak is an IdP that can be self-hosted within your own environment and works perfectly out of the box with VCF SSO and this blog post will show you how that set it up without relying on a hosted IdP solution!
Gotta catch them all!? ?
Looks like I will be adding another identity provider to my existing collection of IdPs (Authentik, KeyCloak, Synology SSO, Pocket ID, Zitadel and Kanidm) that can be used with vCenter Server and VMware Cloud Foundation (VCF) Identity Federation.
Authelia is another free and self-hosted IdP solution, which also supports Time-based one-time password (TOTP) out of the box and all configurations are managed in a couple of configuration files as there is no administrative web UI.