What happens if Single Sign-On (SSO) is not enabled in an environment?

If Single Sign-On (SSO) is not enabled in an environment, users typically receive instructions to create a password. This is because, without SSO, each user must have a unique credential in order to access the system. When SSO is not in place, the organization must ensure that users can still authenticate themselves manually, which often involves guiding them through the process of creating a password for their account.

In environments where SSO is implemented, users can log in using one set of credentials across various applications, simplifying the authentication process. However, if SSO is absent, the system reverts to traditional authentication methods, necessitating a password creation process to enable user access. This approach ensures that even in the absence of streamlined SSO capabilities, users can still engage with the system securely.

The other options do not align with the typical outcome of not having SSO. For instance, no action being taken does not reflect the need for authentication. Initiating a manual approval process isn’t standard in this context since user access generally requires immediate authentication. Redirecting users to a different page is not a common protocol when SSO is not implemented, as users typically remain on the login interface to complete their authentication.