Print

Print

Before we get much further let's do some basic stuff. First, what is the actual contents of authinfo when a token is used to populate that field. We already know what it is for non-token scenarios but we need to document what it is for token scenarios. Second, how is this field populated? That is, what should be called with what API or should one get some other structure and populate the filed from that? It's all pretty much a black box right now.

—
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/1987/1498518558@github.com>

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