[Bug 59910] certificateKeyAlias required to be set

2016-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 Remy Maucherat changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 59910] certificateKeyAlias required to be set

2016-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 --- Comment #5 from Mike Noordermeer --- That may be the case, but a PFX file almost always has a password, so people set the password. Nobody knows what the key alias is though (and nobody specifies the name when creating the PFX). This is jus

[Bug 59910] certificateKeyAlias required to be set

2016-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 --- Comment #4 from Remy Maucherat --- Thanks for the feedback, but I disagree with that. All of our current examples and howtos use "tomcat" as key alias, and "changeit" as password (it is the hardcoded default, just like "tomcat" is hardcoded

[Bug 59910] certificateKeyAlias required to be set

2016-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 --- Comment #3 from Mike Noordermeer --- I wouldn't be too happy with that, as most people are not even aware of the fact that a PFX can contain multiple certificates and keys. And in that case it would probably be better to require the user to

[Bug 59910] certificateKeyAlias required to be set

2016-08-02 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 --- Comment #2 from Remy Maucherat --- This was changed since it's a lot harder to do properly with OpenSSL and so it needs an alias name. For consistency, it could be best to keep the new default for both JSSE and OpenSSL, and fix the document

[Bug 59910] certificateKeyAlias required to be set

2016-07-29 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=59910 --- Comment #1 from Mike Noordermeer --- Btw, this is with JSSE and a PFX certificate containing only one entry. -- You are receiving this mail because: You are the assignee for the bug. --