Remove login options?

[Chris Green]

Is there anyway to remove the login options that we don't want to use for our organization from our Atlassian login page? 

For example, we don't want to use Continue with Google, Apple, or Slack.

[Mikael Sandberg]

No, you have no control over that, those are the options that everyone have using Cloud. You can work around it if you want to use SSO by subscribing to Atlassian Access and connect it to your user provider.

[Chris Green]

Well that's disappointing. We only want to use our SAML SSO to let users log in, except for a few outside vendors we have part of a separate auth policy. 

We have Atlassian Access......but our login screen still displays all login options. 

[Mikael Sandberg]

It doesn't matter if you have Atlassian Access or not, the log in screen is the same for every customer and cannot be configured to be specific per customer. We have Atlassian Access to and solves this via SSO, that way only external contractors have to go through start.atlassian.com

[Paul Pottorff]

Has anyone tried enforcing SSO on default policy? Our Atlassian rep tells us that this makes the others go away, if the user tries to go to a site in an sso enforced enterprise.

[Chris Green]

We have SSO enforced on a Default Policy and have no issues. What do you mean by "this makes the others go away"? Do you mean the users you don't want to force to use SSO? In that case, we setup a separate policy and add those users to that policy and leave single sign-on turned off. 

Chris

[Mark Gillespie]

Also asking about this.   We have Atlassian Access, and still presented a long list of login options.

Atlassian don't seem to understand how many support calls this sort of things generate.

"I tried to log in using Microsoft option and I don't have access".  It's so bad, we have to send department wide emails telling users what options to use and what not to use.

In general, after being forced by Atlassian away from self hosted Confluence, using the Cloud is turning out to be lots of hassle, when it should be LESS hassle.

[Anthony Casas]

Im bumping this too, because its causing my leadership team to question the validity of our new SSO implementation as well. The point of enabling and enforcing SSO is so that these options do not show up, even when disabling it completely on Local and IDP Authentication policies.