Ok, so my assumption was wrong, you couldn't pass credentials in the
URL to Ruby SRU's initialize method (well, you could, but it wouldn't
This has been updated and I just released v 0.0.8.
On Mon, Apr 11, 2011 at 10:13 AM, Ross Singer <[log in to unmask]> wrote:
> Hi Sebastian,
> I can only speak for Ruby-SRU, but I'm fairly certain authentication
> played almost zero part in the design of it. You *can* set up basic
> authentication for a client (I think!) if you pass your credentials in
> the base url:
> client = SRU::Client.new("http://[email protected]:example.org/sru")
> This should work (although nobody has ever requested this
> functionality or complained in Ruby-SRU), but I haven't actually tried
> it (do you have a basic auth protected server to try against?).
> Anything besides basic auth (digest, token-based, ldap, etc.) would
> require a bit of refactoring to accommodate.
> On Mon, Apr 11, 2011 at 9:44 AM, Sebastian Hammer <[log in to unmask]> wrote:
>> We are setting up a SRU target that is intended to allow for
>> username/password authentication. When we have done this between
>> instances of our own software, we have used HTTP Basic Authentication
>> (see http://www.loc.gov/standards/sru/resources/authentication.html).
>> However, it is not clear to me what current practices are in this area,
>> and I'd like to set up a server that supports as many existing client
>> applications as possible.
>> Does anyone have a sense of what's most commonly supported by commercial
>> or OSS SRU clients today?