Well, that seems to backtrack on everything that we agreed on and that was
not to branch at the security level as that would essentially create two
copmplete and different services that would likely never converge. A total
mess if you ask me. We also agreed, well thought we did, that we would use
the SSS approach to carry through the the credentials as this was
uniformaly the way it was expected to be done. Now I see that is off the
table. Does that mean any more development for SSS is also off the table
(i.e. not desired)? Obviously, I don't agree with this approach unless you
all want to create a big mess. I'm not into big messes.

Andy

On Mon, 24 Feb 2020, Fabrizio Furano wrote:

> Hi,
>
> I think that your comment tells it all:
>
> "useful when an internal filesystem (such as XrdPss) does not have the ability to forward an XrdSecEntity but might understand macaroons."
>
> The approach is solid, it's a pity that the internal theoretically orthodox approach (i.e. through XrdSec) has to be worked around in such ways, and I totally see the point for this kind of things.
>
> I can merge it, will you please fix the build errors Brian?
>
> --
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/pull/1115#issuecomment-590264742


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/pull/1115?email_source=notifications\u0026email_token=AA7NRDVLTZ3U2KZCIUY7DBDREREY5A5CNFSM4KHD2E2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZ2NEI#issuecomment-590587537", "url": "https://github.com/xrootd/xrootd/pull/1115?email_source=notifications\u0026email_token=AA7NRDVLTZ3U2KZCIUY7DBDREREY5A5CNFSM4KHD2E2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZ2NEI#issuecomment-590587537", "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