K
Kinde•7d ago
prullebakje.

Error 4179 when logging in with Microsoft

Hi, i'm getting since a few days the error code 4179. I already changed the secrets for the Microsoft connection. But without any luck.
5 Replies
Ages - Kinde
Ages - Kinde•7d ago
Hey, Thanks for reaching out. The error code 4179 usually means "Social OAuth callback - error exchanging token" typically occurs during the token exchange process. Could you tell us what framework, SDK and version you're using? In the mean time, could you also check: - Verify your client_id and client_secret are correctly set. - Ensure your callback URLs are properly configured in your application settings - Verify the redirect_uri matches exactly what's configured in your app settings Let us know and we can take a closer look. Thanks
bpdigisub
bpdigisub•7d ago
Hi there, I am experiencing this issue as well. I've not yet redone client ID and secrets.
prullebakje.
prullebakje.OP•6d ago
I not used the the client_id and client_secret fields. I left them blank. But then the error showed up a few days ago. Now I registered my application, but still no difference. Callback urls are working.. It does not have anything to do, with that i'm on the free plan? Still having the error.. Rotated the secret. Nothing worked so far
prullebakje.
prullebakje.OP•6d ago
Found the issue. When switching to "MultiTenant" it works again 🙂
No description
Ages - Kinde
Ages - Kinde•6d ago
That's great to hear...

This multi-tenant configuration allows the authentication to work across different organizational directories, which is typically what's needed for proper OAuth token exchange.

Let me know if any assistant needed from our side.

Did you find this page helpful?