If so, I can plop a pointer to an authorization object in the XrdOucEnv object passed to the protocol plugin
I think this would work; at least, would be willing to test for v5.
I do eventually need both a pointer to the authorization object and for the filesystem object (for XrdHttpTPC
, not Macaroons).
For v4 versus v5: I'm OK with showing this works with v5 and seeing how much nasty code this allows us to remove -- and then making a decision about a backport.
—
You are receiving this because you commented.
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