Print

Print

@cantrip : are you enforcing specific authentication method on the client side by setting either the XrdSecPROTOCOL envar or specifying the xrd.wantprot cgi element in the URL?

The problem is the server asks for authentication either with sss or unix

[2022-10-11 13:28:56.222309 +0100][Debug  ][XRootDTransport   ] [st-096-hh151b28.cern.ch:1095.0] Authentication is required: &P=unix&P=sss,0.+13:/etc/eos.keytab

and the client is not trying any of those because we don't seeTrying to authenticate using unix in the logs. The unix authentication is always possible (without any special credential), which makes me think there's a client side setting that prevents the client to go ahead with the unix authentication.

—
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/1755/1275891119@github.com>

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