-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement and/or Verify Subject Alternate Name functionality #26
Comments
An experience document concerning this issue can be found at http://www.egcf.eu/site/wp-content/uploads/2012/11/SAN-Experiments.doc. |
Hi, Can you repost it as a PDF? Thanks, Brian |
Repost the comment or the document? On 27-Mar-13 15:04, Brian Bockelman wrote:
Marius Joldos |
Ah - the document please. I had issues opening it. |
Alright - so it appears SAN definitely is not implemented. Would you have time to contribute a unit test and/or implementation? |
On 04/01/2013 04:28 PM, Brian Bockelman wrote:
Marius Joldos |
Subject alternate names allow a single certificate to be valid for several service names. This is very useful if a single service has several load-balanced hosts (see rfc2459 section 4.2.1.7 on subjectAltName).
We should whether verify a JGlobus-based server and client can properly handle subjectAltName extensions. If not, fix any limitations found.
The text was updated successfully, but these errors were encountered: