Hi,

is globus caching user mappings?
I'm running GT 4.2.1 with VOMS support. I added VOMS PIP/PDP to GRAM
service, it's factory, RFT, and it's factory. Mapping standard proxy and
proxy with VOMS AC works using Java- and C-based components. But, I get
some wrong mapping when changing my proxy certificate. Using VOMS proxy
and switching to VOMS-less proxy everything works as expected, but if
switch from standard proxy to VOMS proxy back again I sometimes get
still mapped to standard proxy's account. Restarting the container fixes
this immediately. Is there some kind of caching mechanism and would it
be possible to disable it? Is some securityContext/resource reused I
could destroy before?

Regards,
Benjamin

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to