fix: duplicate SSO login buttons when SSO provider or SAML login is enforced

[maxbelm]

Problem

This PR attempts to address #17324

In writing up this PR a couple assumptions were made:

1. That we should not display the SocialLoginButton component if an SSO provider is enforced
2. That we should not display the SocialLoginButton component if SAML is available

The thinking behind those assumptions is: a user will have a clearer, more streamlined login experience when they only see the enforced options for login.

Please let me know if any of the assumptions are incorrect, happy to adjust the work as needed!

Changes

SSO Enforcement (Google):

SAML available:

No SSO enforcement or SAML:

How did you test this code?

Since this is a frontend UI change and there are stories present for the login component, I went with a manual testing approach. Happy to adjust that approach if we'd like!

Testing explanation:

Previously there was one value that influenced the SocialLoginButton component's display:

• preflight.available_social_auth_providers

As of this PR, three values will influence the component's display:

• precheckResponse.saml_available
• precheckResponse.sso_enforcement
• preflight.available_social_auth_providers

In order to test this, I modified these values inline to observe that the UI behavior was as expected.

The Google SSO enforced picture involved setting the values to the following:

• precheckResponse.saml_available = false
• precheckResponse.sso_enforcement = 'google-oauth2'
• preflight.available_social_auth_providers = { github: true, gitlab: true, 'google-oauth2': true }

The SAML available picture involved setting the values to the following:

• precheckResponse.saml_available = true
• precheckResponse.sso_enforcement = null
• preflight.available_social_auth_providers = { github: true, gitlab: true, 'google-oauth2': true }

The social login link picture involved setting the values to the following:

• precheckResponse.saml_available = false
• precheckResponse.sso_enforcement = null
• preflight.available_social_auth_providers = { github: true, gitlab: true, 'google-oauth2': true }

Note: The StoryBook stories for the Login component look correct as well.

[raquelmsmith]

This looks great, thanks for the detailed PR @maxbelm!

[maxbelm]

@raquelmsmith I really appreciate the quick feedback and review!

It looks like E2E required tests and docker image build are erroring out:

Unable to exchange open-source pull request OIDC token for temporary Depot token: Error: OIDC auth challenge ... timed out 
...
Error: failed with: Error: missing API token, please run `depot login`

I'm not too familiar with this, is this something the team has encountered before?

[raquelmsmith]

Hm, that's because your fork is technically outside of our repository (as is expected). Let me check with the rest of the team to see what to do here.