@abh3, yes, root CA with SAN extension seem to work also for other clients. What's the best course of action in this case, I'd say we can ask Polish folks add SAN alternate name as they had in older root CA. But still, I wonder whether this is an mandatory field for the older client pass through some validation? If that field is empty it could be ignored, no?

@stlammel, do we have GGUS ticket or can we create one asking Polish colleagues add this part into the new root CA:

            X509v3 Subject Alternative Name: 
                email:[log in to unmask], URI:http://www.man.poznan.pl/plgrid-ca/

Or ask them why this was removed? Maybe there is reason for it and also, we just think this solves the problem, but not guaranteed.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1110?email_source=notifications\u0026email_token=AA7NRDRVDYLNZDUNO7D5QSTQ6ZRXBA5CNFSM4KGHOCA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJOK6LA#issuecomment-576499500", "url": "https://github.com/xrootd/xrootd/issues/1110?email_source=notifications\u0026email_token=AA7NRDRVDYLNZDUNO7D5QSTQ6ZRXBA5CNFSM4KGHOCA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJOK6LA#issuecomment-576499500", "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