use Sam Morisson's SLCS Delegation Service (SDS) by going through the
following steps...
1. user shib logons to portal
2. portal redirects user to SDS service
3. SDS generates token and gets user to send this to the Portal
4. portal uses this information to generate a private key and
certificate request
5. portal sends request and token to the SLCS
6. SLCS sends a certificate back to the portal
7. the portal generates a proxy and stores in myproxy. the portal also
randomly generates a myproxy username and password for the proxy that will
be stored in the repo
8. the username and password is what we'll now use on the WS end to
check if the user can use the service.
authenticating to the DTS WS doesn't necessarily mean that users will be
able to have access to the remote storage locations he wants to transfer
file from/to. Unless he also provided valid credentials in accessing the
source and destination locations in the DTS JOb definition document, what a
user will do if he successfully authentiated to the service is to only
submit a job that might always fail.
Original issue reported on code.google.com by
gerson...@gmail.comon 6 Nov 2009 at 4:40