Print

Print

The issue here is that the server wanted the client to try the protocols in "ztn gsi' and, yes, the message about ztn failure due to non-TLS is forcibly displayed. That may not be the best option but we are working on figuring out how to display auth failures only when the whole authentication stack fails. It's not an easy problem, You can avoid this problem by reversing the order (i.e., gsi then ztn). Then you won't get the ztn error message (gsi never prints out error messages - another problem altogether). So, yes, we know the problem but we have yet to come up with a satisfactory solution.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1927/1441353949@github.com>

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