Correlating events between clients and servers

[Werner Strydom]

Hello,

Consider a suite of applications (web sites, browser and desktop applications) that uses DotNetOpenAuth to support OpenID 2.0 and OAuth 2.0.  Suppose there are a number of QA personell testing the system and one finds a problem and tries to extrapolate the root cause from the server and client logs.  

Is there a way to tell DotNetOpenAuth to correlate related requests and responses with a correlation id?  For example, suppose I want to request an access token. I'd like to pass a correlation id along so that DotNetOpenAuth can write that to the logs and allow me to correlate events on my client with the events on the server for the request of obtain an access token.

Thanks,

Werner

[Andrew Arnott]

There isn't an automatic way to do that today, but that feature would be very cool.  

You may be able to do this by hand by adding a callback argument to your OpenID RPs and to your OAuth clients, such that it would appear in the URLs on both sides.  But that wouldn't cause it to add the identifier to every single log message, which it sounds like you're asking for, and would be the ultimate feature.

I think this deserves some brainstorming on how we could achieve it.

--
You received this message because you are subscribed to the Google Groups "DotNetOpenAuth" group.
To view this discussion on the web visit https://groups.google.com/d/msg/dotnetopenid/-/N-5kxqUp6JMJ.
To post to this group, send email to dotnet...@googlegroups.com.
To unsubscribe from this group, send email to dotnetopenid...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotnetopenid?hl=en.

--
--
Andrew Arnott
"I [may] not agree with what you have to say, but I'll defend to the death your right to say it." - S. G. Tallentyre