.net - DotNetOpenId — Getting replay attack failure with programmatic and web logins -


I'm adding optional OpenID authentication to the system. Everything works smoothly with DotNETOpenID, however, I get a problem when:

  1. The user logs into the web application using a standard login (formattentation)
  2. The user adds some openIDs to the account (we use programmatic open-reads to log on here to obtain the claiming identity)
  3. The user logs from the log-off form attestation and Op With ID (using the Login control) back log.

In the last step we get an error of a replay attack. I suspect that there is some information left in the OpenID application store (can be used for requests) Is used to achieve the previous request instead of starting.

Can anyone help in highlighting some problem here?

If the problem is that I have understood it, then how can I clear the information of this specific state successfully after using OpenID using Programmatic Long (seeing that I have a hand Received a successful request from)?

Which provider are you testing against? Honestly it seems like most likely guilty party in this case because it creates openid.response_nonce value; Another possible location to see if you are maintaining all the open-eyed (by the spot). * The query string parameter in the URL between first and second login? For example, before users enter their OpenID on their second login page, their openid. * Parameter in the URL of the page? If yes, then this may be a problem and it can be decided by your programmatic page, which results in a clean redirect to get rid of them after the login attempt.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -