toopher / toopher-issues Goto Github PK

I have successfully managed to integrate the Toopher IFrame with my own CAS application. However, I have trouble resuming the flow session when pairing fails. I can see that the flow tries to authenticate the user and that fails correctly because my user doesn't yet exist. Then, the flow tries to pair the user and generates the page that allows me to download the apps and start pairing. I simply continue to pair, and provide an invalid pairing phrase. When I press enter on the pairing input box, I get a message that the paring phrase is invalid which is correct, but then the screen turns blank.

What is the expected behavior here? Should the flow resume and put me back in a state where I can reauthenticate? Is it expected of me to put a "back" button somewhere on the page to allow the user to do just that? Is there way for the CAS app to be notified when pairing fails so that I can navigate the flow to a different place?

Moved from here: toopher/toopher-cas#1

SMS authentication does not have time to reliably complete within the current 60-second timeout

5/14/14 - Initial Email report

internal issue 17

From the "Paired with Toopher" screen, if you click "Unpair Account," then "Unpair Device," the resulting screen shows a "Recover Pairing" button, even though we didn't pass an e-mail address when we created the iFrame.

5/14/14 - Initial email report

Internal issue 18

upon successful pairing, one can use the browser's back button to return to the first pairing page and then create a second pairing

5/13/14 - Initial email report

internal issue 16

• Add the word “Texting” to the “Pair with SMS” button on the pairing start page. For example, “Pair with SMS Texting”. If space is an issue, it could be shortened to “Use SMS Texting”. Many of our users do not understand what SMS means but do understand the term Texting.
• Provide examples of acceptable entry formats for mobile numbers on the Pair with SMS page. This would relieve confusion users had over how to enter their mobile number.
• Make the error message text more user-friendly when an invalid pairing phrase or mobile number is entered on the pairing page. Currently it reads, “Bad Request: Could not determine pairing token type”. End users do not understand what that message means and what to do next. An alternative could be, “We’re sorry, but we couldn’t understand what you entered. Please try entering your pairing phrase or mobile number again.”
• On the Authenticating with Toopher wait page, change the text from “Waiting to authorize Log In with Toopher” to “Please authorize this authentication request on your mobile device to continue” (align with the language used on the pairing wait page). End users need guidance on when they should take action on their mobile device.
• On the Authenticating with Toopher wait page, add text above the “Enter OTP” button to explain when the user should click on that button. For example, “Device doesn’t have connectivity?” The “Pair with SMS” button on the pairing page start page has a similar type of message above it. End users were confused about when or why they would need to click on the OTP button.

Request completion by 03 Jul 2014