> so the remote site issues a challenge. do you just pass it on to your user at
> her web page, or have you cached her credentials?
Currently I imagine that the credentials (which may be a Grid proxy
certificate, boo hiss) will be cached on the server. I was thinking
that the user would log on to my web app, thereby creating a session
object in which we can cache credentials.
Jon
2009/1/20 John Caron <caron@xxxxxxxxxxxxxxxx>:
>
>
> Jon Blower wrote:
>> Hi John,
>>
>>> Are you managing a database of user/password credentials for the various
>>> remote sites?
>> Yes, but currently I'm limited to one user/password combination for
>> each site, which won't work for me in a particular project.
>>
>>> Another design is that ncWMS has a single logon to each of your remote
>>> sites.
>> Unfortunately I can't do this. The remote site needs to know exactly
>> who is using ncWMS.
>
> so the remote site issues a challenge. do you just pass it on to your user at
> her web page, or have you cached her credentials?
>
--
Dr Jon Blower
Technical Director, Reading e-Science Centre
Environmental Systems Science Centre
University of Reading
Harry Pitt Building, 3 Earley Gate
Reading RG6 6AL. UK
Tel: +44 (0)118 378 5213
Fax: +44 (0)118 378 6413
j.d.blower@xxxxxxxxxxxxx
http://www.nerc-essc.ac.uk/People/Staff/Blower_J.htm
