Hi @bbockelm,

I think that properly modifying the WLCG JWT compliance tests and the expectations in terms of token scopes make this requirement obsolete for EOS. Believe me, I am also not of fan of sending such raw token info down the line to EOS, but I was under the impression that the compliance tests were "set in stone" and agreed upon by the wider community - and at that point passing this info to EOS was the only way it could work.

Nevertheless, it's good to know this exists ... who knows what the future will bring!

Thanks,
Elvin

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1578#issuecomment-997463642", "url": "https://github.com/xrootd/xrootd/pull/1578#issuecomment-997463642", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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