Okta stops after authn request on custom domains

Questions
1

React Application is working well on localhost but not on dev-server.
Flow stops after authn call. No success/error response. loader spinning endlessly.
not see any iframe.

dummydomain
dummydomain1346×686 85.8 KB

localhost
localhost1361×680 101 KB

2

Hi there. Thanks for the network SSs, any chance there are errors showing in the console?

3

Hi,
Showing no error in console.

4

Thanks for confirming. The fact that it’s working locally and not when deployed makes me curious if there’s something going on with 3rd party cookies. Are you blocking 3rd party cookies in your browser? And if so, does it work if you temporarily unblock them?

5

Hi Cale,

I have allowed all cookies in browser and still same result.
Attached screenshots for your reference, you can check console as well.

Screenshot_1
Screenshot_11980×744 258 KB

Screenshot_2
Screenshot_21908×786 289 KB

6

I am running into exact same issue. Works on localhost but not on custom domain. I am upgrading from version 4.4.4 and never had such issue before.

7

Hi @nsheikh

I am using these versions:
@okta/okta-auth-js version: 5.3.1
@okta/okta-react version: 6.1.0,
@okta/okta-signin-widget version: 5.9.4,

8

@Cale, do you have any suggestions here? The issue can easily be reproduced even using the code sample on the Okta website below:

Okta Sign-In Widget Guide | Okta Developer

9

@krishnabardoliya I see in the first screenshot your site is using HTTP, you should be using HTTPS and that could potentially fix your issue.

@nsheikh I don’t know if this applies to you as well.

10

@Cale, I am testing with HTTPs and it’s the same issue.

11

@Cale, is there any workaround for this? Can’t really use version 5.x, I am surprised others are not running into this issue.

12

@nsheikh I currently can’t repro the issue you’re experiencing. Yours also does not log any errors in the console and you aren’t blocking 3rd party cookies at all?

13

@Cale , correct there is no error in the console and we are not blocking any 3rd party cookies. I don’t believe the issue is specific to 3rd party cookies since I would have expected it would have had same issue with version 4.4.4. Some screenshots below

image
image712×765 53.9 KB

image
image1306×746 29.1 KB

image
image1687×327 22.9 KB

image
image1141×310 8.01 KB

14

There were some breaking changes going from 4.x to 5.x. If you have it working in the latter but not the former, take a look at this migration doc and see if anything stands out to you:

It could be that you are using methods that don’t exist or have different names in 4.x

1 Like
16

Thanks, this helped. Seems like showSignInToGetTokens() doesn’t redirect anymore and showSignInAndRedirect() needs to be used.

17

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.