Directory Programming .NET

Is there any reason that someone can think of as to why a single user would get the duplicate request error but nobody else does?

I can logon with this user's credentials and have no problem.

I thought this might be a cookie related issue but I am having a hard time figuring out where the point of failure is in addition to how I might reproduce it.  It is a bit difficult to troubleshoot as this user is an external user that I do not have direct contact with.

Any suggestions will be greatly appreciated.

Thank you,

Jason

These things can be very frustrating. My production system hums along 24x7 with almost no complaints from users but my production logs are always full of duplicate token errors. I don't believe it is possible to make them all go away.

The only way to know for sure what is happening is to record the HTTP headers of a failed logon and examine them. This is what I usually recommend. If you post them here, we can diagnose them for you.

The problem in a situation like yours is collecting them. If you can't repro and the user is remote, you may need them to repro for you and getting them to properly use a HTTP collection tool may be a challenge.

You might start by asking what browser they are using and if they have any settings in place that might disable cookies.

Also, you may run into issues on the target application if the issued cookie path is different from "/". If you have a path in there, that will be treated as case sensitive by the browser. Those types of errors are easy to repro but sometimes you may not see the exact URL the user is using on the target app and thus won't notice this type of thing.

Being an external user, is there any reason that their original referring URL would somehow be different going to the Federation server?

I kept getting that error when we two different versions of the same app on a different URL going to the same federation server, but both apps were telling the federation server the same return URL because I had forgotten to change it in the other version. So starting at App URL A would send back to App URL B, but since I had not originated at B, B was confused and sent me back again to Federation causing the duplicate request.

If you could provide an HTTP header trace of this interaction, we could easily look at it and explain exactly what was going on. Everything you need to know is in the headers for a problem like this.

Unfortunately, it is hard for me to be really specific in recommendations without seeing that.

If you can repro this easily, then getting the headers should also be easy (Firefox live headers plugin, IEHTTPHeaders, Fiddler2, etc.).

Today students more often use custom writing as its good help in their studying.