0D51Y00008W2mHgSAJOkta Classic EngineSingle Sign-OnAnswered2024-04-15T11:05:05.000Z2020-05-15T21:50:29.000Z2020-05-18T04:48:53.000Z

qz06g (qz06g) asked a question.

Okta widget + B2B SSO + B2B MFA

Can the following use case be supported by Okta?

 

We have a cloud product offering for B2B customers. Our cloud site is publicly available and currently the authentication is via simple userid/password. We would like to redesign our authentication flow to redirect B2B users to their org's IdP and then MFA into our app

 

Thanks

Nik

 


  • qz06g (qz06g)

    To clarify, the flow we are wanting to design is

    (1)B2B user hits our URL

    (2)Okta redirects user to user org's IdP where they authenticate themselves

    (3)User org IdP redirects to our URL

    (4)Okta requires B2B user to go through MFA

     

    Thanks

    Nik

    Expand Post
  • StephenW.90637 (Atlas Identity)

    Hi Nik. This is definitely possible and we have implemented it several times. Please do ping me if you need any specific instructions or troubleshooting for any attempt that you’ve made to get this working. in preparation for this, I’d suggest you think about one key item. How are you going to identify these B2B partners? Will each partner have a unique email domain? Will they come from a unique set of IPs?

    Expand Post
  • qz06g (qz06g)

    Stephen,

     

    Thanks for your response. I was able to confirm via a quick and dirty POC that MFA can be layered on top of an external IdP flow initiated at the SP(us). Regards your other question our mechanism for external IdP discovery and redirect will be hybrid. I.e. Some B2B customers will be using their corporate issued e-mail address whereas some will be using non-corporate e-mail id's(yahoo, gmail, etc).

     

    I have not yet dived into the API yet but I'm hoping that we can construct an experience that resembles office365 where upon hitting the sign in widget, user is presented with a screen that asks for e-mail address. On entry of the e-mail address, my assumption is that on the back-end, Office is doing IdP discovery and routing the user accordingly.

     

    Technically we have to solve for the following use cases

    (1)For some B2B users we are the IdP and for some we are the SP

    (2)Some users will have a corporate e-mail address as the userid

    (3)Some users will have a non-corporate e-mail address as the userid

     

    So I'm hoping that we can fetch the registered IdP via Okta API and route accordingly(either to an external IdP with callback to us or continuing the flow and getting from user their pswd and MFA creds)

    I'm hoping that we can make a back-end call to Okta API on user entering their e-mail address, retrieve all the datapoints about the user in our system and route accordingly.

     

    Expand Post
This question is closed.

Recommended content

No recommended content found...