I've got a very minimal AT implementation done if anyone wants to
experiment with it for their client code.
Send an empty <authenticationTokenRequest> to the server and it will
respond with <authenticationTokenResponse>. This has a <token> field,
which has two parameters, value and ttl.
Put the value into the srw:authenticationToken SOAP header and you're
away.
eg:
<Envelope><Body><authenticationTokenRequest/></Body></Envelope>
<Envelope><Body><authenticationTokenResponse>
<token>
<value type="string">asldkjfasldkfja;sdlfkj</value>
<ttl type="integer">600</ttl>
</token>
</authenticationTokenResponse></Body></Envelope>
Nothing actually /needs/ the authentication tokens, btw, so everything
will work as expected with or without one. [I hope:)]
Rob
--
,'/:. Rob Sanderson ([log in to unmask])
,'-/::::. http://www.o-r-g.org/~azaroth/
,'--/::(@)::. Special Collections and Archives, extension 3142
,'---/::::::::::. Twin Cathedrals: telnet: liverpool.o-r-g.org 7777
____/:::::::::::::. WWW: http://liverpool.o-r-g.org:8000/
I L L U M I N A T I
