Authentication branches feature in OpenAM 13

This topic has 1 voice and 0 replies.

  • Author
  • #18702
     Pradeep Babu

    Hello Everyone,

    We have been working on a requirement for providing authentication branching in OpenAM version 13. Made progress but hit a problem while redirecting to the target application after submitting the MFA OTP.

    Logic is as follows:

    1) Have an authentication chain with kerberos as first level of authentication and OTP options custom auth module as second auth module
    2) OTP options custom module has Confirmation callbacks & redirectcallbacks, so user can select the OTP option that they would like to invoke and then the selected module URL would be replaced as the RedirectCallBack URL
    3) After the selection is made and RedirectCallBack URL is replaced, individual OTP module URL (configured in OTP options custom auth module) is set as setLoginSuccessURL(this.redirectUrl)

    This works well as an Authentication chain testing. If there is a gotoURL or Relaystate, it redirects to the target URL without requesting the OTP code. ANy suggestions on how to get past this problem.

    Thanks & Regards,
    Pradeep Babu

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

©2021 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?