Microsoft Entra ID (OAuth 2.0) - Always show sign-in button
My client set up Entra ID OAuth for Kinde (we also still have email + code login enabled for the app), and it seems like login works fine and automatically redirects any user with an email configured under home realm discovery to the M365 login, but we'd like to enable the "Sign in with Microsoft" button if possible. When I enabled the "Always show sign-in button" under the Entra ID configuration and hit save, nothing changes on the Kinde auth login page, and when I return back to the OAuth configuration, the button is disabled again. I've tried this a few times over the past 24 hours, and it keeps disabling itself after saving the change. Am I understanding how this should work correctly? Any information or advice would be appreciated!
7 Replies
Hey Ryan, certainly sounds like you have found a bug with the toggle not being maintained. I will get the team to look into this as I have been able to replicate it.
Is there a reason why you would like to combine the Entra ID with the Microsoft login? Do you also want to add Microsoft Social SSO? Will your client be setting up unique Entra ID connections?
Is there a reason why you would like to combine the Entra ID with the Microsoft login? Do you also want to add Microsoft Social SSO? Will your client be setting up unique Entra ID connections?
Awesome, thank you!
Sorry, I shouldn't have mixed up the terms there - they will only be using the single Entra ID OAuth connection to authenticate into the app (and a few users who aren't in the domain [like me] will just have the standard Kinde email + PIN login). They won't be adding the Microsoft Social SSO or any other Entra ID connections.
Hi Ryan, thanks for answering my questions. We have deployed a fix to the issue that you were seeing, able to test again to make sure it working on your end?
Perfect, thanks for that! I enabled it about an hour ago, and it has stayed enabled - but I don't see the login with Microsoft or Entra ID button yet. I did try opening it in a private browsing window to see if it was just a cache issue. Is there something else I'm missing or should do to get the button to appear?
Mmmm, is this how you have it setup?
Yep, exactly! I actually just came here to say that it's fixed now! So if you all made some changes on the backend, thank you!
Not a problem and glad its working for you now