Print

Print

[...] It's also what gets passed to security extractors and what worked in 4.x.

From the tests I did, I think the main cause of the changed behaviour is switching the secextractor from libXrdHttpVOMS (of which no build against XRootD 5 was readily available in EPEL) to libXrdVoms.
My test showed: XrdVoms with XRootD 4 or 5 does not accept old-style proxies, but XrdHttpVOMS with XRootD 4 does accept old-style proxies. I did not test XrdHttpVOMS with XRootD 5, though, which means my test is inherently flawed, since XrdVoms has only become a fully working secxtractor quite recently (I think).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1247#issuecomment-657850632", "url": "https://github.com/xrootd/xrootd/issues/1247#issuecomment-657850632", "name": "View Issue" }, "description": "View this Issue 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