So, to summarize the ticket so far:

We can enable tracing for the XRootD authorization object (xrootd.trace auth). This is currently missing the information @PerilousApricot is looking for (namely, the DN).
It appears that the DN is put into the authorization object as monitoring information if the -moninfo flag is given to the sec.protocol gsi configuration.
Unfortunately, the monitoring info was omitted from the trace log. Here's a simple PR to do that: #1819

With the above PR, the xrootd.trace auth level includes the following:

http Protocol 'gsi'
http Name 'bbockelm'
http Host '[2600:900:6:1301:5054:ff:fe0b:9cba]'
http Vorg 'cms cms cms'
http Role 'NULL NULL NULL'
http Grps '/cms /cms/integration /cms/uscms'
http Caps ''
http Pidn ''
http Mon  '/DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=bbockelm/CN=659869/CN=Brian Paul Bockelman'
http Crlen 0
http ueid  0
http uid   0
http gid   0
http Attr gridmap.name = '1'
http Attr  = ''

Is that sufficient?

I do really dislike the formatting of the information (split across multiple lines, makes it difficult to grep). Any reason we shouldn't also touch up the formatting?

PS - I agree with @abh3 above -- we likely really want to do a follow-up for request logging since, for tokens, requests are separately authorized from sessions.

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

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