 |
 |
Hi all,
@simonmichal Indeed we were missing the -vomsfun:libXrdVoms.so. Since we have it in, we get the first tuple of attributes as the result, and this is seems fine for the moment (haven't seen any examples to the contrary in the logs).
What was confusing is the fact that without -vomsfun: switch, the sec.protocol gsi config would still extract some VOMS data, because of the -vomsat:1 switch.
However, the extracted values would be mangled together: we mostly saw the combination of /cms/GGUSExpert:production (mixing up roles and groups) end up in EOS vid mapping (instead of /cms:production).
Also from our trying out, the -vomsfunparms: would only work with -vomsfun: present.
@apeters1971 that sounds like a good starting point.
Best,
Erich
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1