/opt/vmware/vcloud-director/logs/vcloud-container-debug.log on the VCD Cells shows entries similar to:<DATE> | INFO | pool-jetty-123 | SAMLDefaultLogger | AuthNResponse;FAILURE;#.#.#.#;https://vcd.example.com/login/org/organization/saml/SSO/alias/vcd;http://idp.example.com/####;;;org.opensaml.common.SAMLException: Response issue time is either too old or with date in the future, skew 60, time <DATE> at org.springframework.security.saml.websso.WebSSOProfileConsumerImpl.processAuthenticationResponse(WebSSOProfileConsumerImpl.java:126) at org.springframework.security.saml.SAMLAuthenticationProvider.authenticate(SAMLAuthenticationProvider.java:88) at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:199) at org.springframework.security.saml.SAMLProcessingFilter.attemptAuthentication(SAMLProcessingFilter.java:92) at com.vmware.vcloud.ui.h5auth.filters.CustomSamlProcessingFilter.attemptAuthentication(CustomSamlProcessingFilter.java:30)
This issue can be caused by time synchronization problems between the identity provider and the Cloud Director Cells which cause the SAML login to fail.
The identity provider and Cloud Director Cells must synchronize to NTP servers to ensure their time is in sync.
timedatectl status command as per the documentation, Check the NTP Service Status of Your VMware Cloud Director Appliance.ntpdate <time_server> command completes successfully but the status command shows System clock synchronized: noman 5 timesyncd.confNote: If you encounter this issue in Cloud Director 10.6.x, refer to KB 381873 regarding a known issue with timesyncd.