I don't think it's a buf per se, it's simply someone enforcing a
requirement that TLS must be enabled to use the ztn token (note that the
ztn token appears under the covers so that is likely the source of the
confusion). This may or may not be changeable, I will have to see. I do
appreciate that it's not convenient.

Andy

On Tue, 10 Jan 2023, Bryan Hess wrote:

> I would prefer to not need TLS from the proxy-to-origin traffic since sss encryption protects the token. In my current configuration I must maintain both an sss key and certificates, which seems redundant.
>
> Is this a ztn bug?
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1851#issuecomment-1377373293
> You are receiving this because you were mentioned.
>
> Message ID: ***@***.***>

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1851#issuecomment-1377535722", "url": "https://github.com/xrootd/xrootd/issues/1851#issuecomment-1377535722", "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