Question on Multi Context Broker

[Paul Hethmon]

Nanda,

What you would need to do is return a false result on the initial username/password verification to the MCB, but keep track of the actual success internally. Then the MCB will call the display login method again and you can present the second screen for the OTP value. Then the user submits the second screen, you validate and return true to the MCB.

Paul

From: Nanda Kumar <NKK at FISCHERINTERNATIONAL.COM<mailto:NKK at FISCHERINTERNATIONAL.COM>>
Reply-To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Date: Wednesday, October 30, 2013 11:55 AM
To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Question on Multi Context Broker

Hello,

I am trying to see if the Multi Context Broker can be used for the following scenario:


I understand that an MCB submodule (bean) should implement the MCBSubmodule interface which provides a function to display a login form and another to process the login.
I also understand that an authentication context can have one method and that method can be mapped only to one bean(MCBSubmodule implementation).
What if I want to show one screen with the username and password and then if the authentication based on this information is successful, show another page with an SMS pin.   The user is fully authenticated
only if the pin is also successfully verified

If multiple forms cannot be displayed using a single submodule, the user can enter the username and password and click on something to have it verified and have the pin sent to the user.  After the user receives the pin it
can be entered on the same page below the user name and password and then click on something to verify the pin.  But then in this case, the processLogin function of the MCBSubmodule interface will have to be called twice.

Is this scenario supported by the MCB or is there a mechanism to implement this scenario using the MCB?  Any help in this regard is greatly appreciated.

Thanks
Nanda
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20131030/d492ce24/attachment-0001.html