idp auth module plugin

[Paul Henson]

So for the rapid identity push authentication you need to make an API 
call to initiate the push authentication (called ping), and then poll 
for the status with additional API calls until it either succeeds, 
fails, or times out.

I'm trying to decide how to best handle that within the authentication 
flow. I'd like to display a status page indicating that a ping is in 
progress, so after ping is selected I could jump to to a view state 
displaying the status info, and have it auto submit to proceed to an 
action state that initiates the ping and waits for success. Assuming the 
success or failure is determined before a browser connection would 
timeout then either the browser moves on to the next step of the 
authentication or gets an error page saying things failed. However, 
there is a requirement to be able to cancel the ping in progress and 
select a different authentication method. If I have a link on the status 
page with an event to allow that, if it is clicked after the status page 
has already auto submitted the proceed event, I assume someone clicking 
on that link while the browser is spinning would end up getting an error?

Any suggestions on the best mechanism to handle this?

Thanks…