Print

Print

Actually, it is by design. The message in question is merely a warning. Perhaps a bit too aggressive since the config said that DNS was supposed to be used but we thought silent bypasses weren't such a good idea. As you should see, this situation simply forbids delegation but otherwise if we can accomplish the required authentication without delegation then all will be fine. By putting in the return statement that possibility is foreclosed. So, in fact, the pull request is not what we really want here.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/pull/1583/c1007837348@github.com>

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