Discourse login in dialog offers log in options that do not exist

I have not enabled any sign in / authentication options other than by simple password or Google in Discourse administrator login settings. However, following a recent update, users are being presented with other sign in options, which of course all fail.

These authentication options (Apple, Microsoft, OpenID Connect, and passkey) seem not even to have any (intuitively identifiable) corresponding admin settings that would allow me to turn them off.

I was able to turn off an unwanted Facebook login option, but that was the only one

Is this a known issue, and how do I prevent options from being offered when they are neither enabled or configured with the necessary keys or secrets? (or when no such settings even seem to exist).

We should not have to create custom theme components or css to hide login options that do not exist.

This is under version 2026.6.0-latest

If you go to Admin > Community > Login & Authentication, do those settings help? For example, OpenID Connect enabled, Enable Google OAuth2 logins, Sign in with Apple enabled and Microsoft auth enabled.

To disable passkeys, see this bit:

Thanks @NateDhaliwal

Those options are not all present there.

In particular there are no settings for Microsoft or Apple at all, at least not that I can see.

so, not only can they not be disabled if they are unwanted, but they can also not be set up to actually work properly if they are wanted.

That rails option is also the sort of thing I was hoping to avoid - administrators should not need to leave the administrator UI to change or test different administrator settings.

What if I want to enable one of those extra login methods in future, but not the others?

did you notice the login and authentication page has several tabs across the top?

The ‘Social logins’ tab is where these setting appear

Thank you!

I thought I had checked there, but obviously not well enough (you have to scroll down)