# Redirect Issue: Successfully Logging in with Okta but Redirected to Okta Dev Dashboard Instead of redirectUri **URL:** \ **Category:** Questions\ **Created:** [January 26, 2024, 7:40pm UTC](https://devforum.okta.com/t/redirect-issue-successfully-logging-in-with-okta-but-redirected-to-okta-dev-dashboard-instead-of-redirecturi/26502 "2024-01-26T19:40:57Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![andrea](https://sea1.discourse-cdn.com/oktadev/user_avatar/devforum.okta.com/andrea/32/2172_2.png) [@andrea](https://devforum.okta.com/u/andrea)\ **Post date:** [January 26, 2024, 8:01pm UTC](https://devforum.okta.com/t/redirect-issue-successfully-logging-in-with-okta-but-redirected-to-okta-dev-dashboard-instead-of-redirecturi/26502/2 "2024-01-26T20:01:06Z")
Are you using an Okta Classic org, or an Okta Identity Engine org? What you’re describing sounds similar to a limitation in Okta Classic that, in a self-hosted widget, Federated Users (e.g. users from an external IdP like Google) will only be logged into Okta, but the /authorize request is not made (this is mentioned in the widget readme [here](https://github.com/okta/okta-signin-widget/blob/master/docs/classic.md#idp-discovery)). If this is an Okta Classic org, there’s a solution for this outlined here: [Social auth redirect not working with Okta Sign-In Widget | Okta Help Center](https://support.okta.com/help/s/article/Social-Auth-redirect-not-working-with-Okta-Signin-Widget?language=en_US) --- _[View the full topic](https://devforum.okta.com/t/redirect-issue-successfully-logging-in-with-okta-but-redirected-to-okta-dev-dashboard-instead-of-redirecturi/26502)._