My intent is to gracefully degrade and maintain state not in a cookie , but rather keep the session information in a HTTPS protected URI, that is repeated for each request.
What authentication systems support this primitive browsing?
Although this question doesn't directly deal with my webserver (and it shouldn't matter anyways) I would appreciate it if you could mention what authentication library works best or doesn't work for a given provider:
A helpful answer will tell me what technology supports or does not support cookie-free sign in, and what supports
.js free sign in
A GREAT answer will tell me the technology and the corresponding library that works with is
WIF ??? with WS-Fed (+SAML Token) Protocol with ADFS Server.
Facebook Integration API:
The idea is that even though an underlying technology may support cookie free and JS free authentication, the corresponding library is implemented in a way that does not support this.
Please contribute whatever knowledge you have so I can triage the information into a nice summary for the benefit of all.