cosign-discuss at umich.edu
general discussion of cosign development and deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: authenticated rss
- To: "cosign-discuss Discussion" <cosign-discuss@xxxxxxxxx>
- Subject: RE: authenticated rss
- From: "Syrigos, Panagis" <syrigos@xxxxxxxxx>
- Date: Fri, 7 Oct 2005 14:58:28 -0400
- Thread-index: AcXLb7itvMYiZYBgQTixelGt5jV/mgAAT8aA
- Thread-topic: authenticated rss
KX509 would be an interesting solution to this.
Panagis Syrigos Tel: (734) 615-6174
System Administrator II Fax: (734) 764-2025
Desktop Support Services Email: syrigos@xxxxxxxxx
Library Information Technology
University of Michigan
And on the 8th day God said, "Ok Murphy, you take over."
From: Cory Snavely [mailto:csnavely@xxxxxxxxx]
Sent: Friday, October 07, 2005 2:48 PM
To: cosign-discuss Discussion
Subject: authenticated rss
We're starting to see more applications in the library for RSS, and the
topic has come up about authenticating for RSS feeds that carry
Obviously we would envision this relating to other authentication
strategies, particularly CoSign, but this (RSS) seems really limited by
tools at this stage. A few can do HTTP Basic Authentication over SSL.
Woo. One nice solution from my perspective would be an RSS reader that
can piggyback on browser cookies, but I haven't heard of any such thing.
It's a little like when we were waiting for good cookie support across
the board...oh boy, Netscape 3 (or whatever). Remember that?
Given the state of the technology, we'd be really interested in hearing
what other folks doing or thinking about authentication for RSS.
UM Library IT Core Services