Okta SignIn Widget returning different responses

Questions
1

Hi there,

I noticed when using the Okta SignIn widget that a different response is returned when passing the client ID, compared to if the client ID is not included. For example:

// with client ID returns token, code, status 
const signIn = new OktaSignIn({
 ...params
  clientId: '${clientId}',
});

Versus:

// without client ID returns user, type, session, status
const signIn = new OktaSignIn({
   ...params
});

Curious if there is a reason for this?

Thanks!
Grayson

2

I believe if you don’t provide a clientId (which is required for OIDC flows) then the widget will just authenticate the user via /authn and then you need additional code on what to do next, such as res.session.setCookieAndRedirect(url).

4

Hi Warren,

That’s very helpful! Thanks for pointing us in the right direction!

Grayson