Herbert Rosmanith wrote:
String remoteAddress = MessageContext.getCurrentContext()
.getStrProp(org.apache.axis.Constants.MC_REMOTE_ADDR);
that's intereresting. is the remote addr the address of the interface the
message
has left the client? if yes, this means that probably private IP addresses would
show up in the message, while a getpeername(2) would probaby return a public
NATed address.
Yes, it's the IP address. I'm not certain how its value is affected by
NAT, however.
I have two questions related to this ...
(1) how do I instruct the service to generate these X509_USER_* files? I *know*
they
exist, but only ... sometimes? Of for some particular jobs? sometimes, the
job-proxy is not there at all.
the "how" is meant: API-wise, C and java, and for both: client and service.
For Java, you might want to look at GlobusCredential, from the CoG kit.
GlobusCredential is used by the grid-proxy-init command, and offers a
variety of constructors.
http://www-unix.globus.org/cog/distribution/1.2/api/index.html
(2) how is the creation of a job-proxy-file implemented in the service?
Sorry, that one is a bit beyond my current knowledge level.
Best regards,
Joel