No they don't for me. We are running on 9.4.18 and do not use SAN. I
have never seen that error.
On 9/15/19 4:31 AM, Sonali Dasgupta
wrote:
Please note that keystores which worked without
SAN in jetty 9.4.8 , now give "No subject alternative name"
errors on running the applications on jetty 9.4.18 . Does that
not signify that SANs are compulsory with jetty 9.4.18 ? Also ,
these keystores already have CN.
Would appreciate a more detailed explanation on
this issue , from the jetty developers. Also , the error seems
fully related to Jetty, since it stems from jetty SSL
Context.
Thanks
Hi,
On Sat, Sep 14, 2019 at 7:05 PM Sonali Dasgupta
<sonalidasgupta95.2011@xxxxxxxxx>
wrote:
>
> Are Subject Alternative Names (SANs) in keystores
compulsory while configuring SSL over Jetty server (version
9.4.18) ?
No.
> Is there a property which on being set , allows SSL
configuration without SANs in the keystore z/
I don't understand this, and it has nothing to do with Jetty
how you
setup your keystore.
If you don't want to use SAN, you just use the CN (perhaps
with a wild
domain) and you're good to go.
> Facing critical issues hence help will be appreciated.
If you need critical support for Jetty, you can lookup
commercial
support from Webtide: https://webtide.com.
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jetty-users
|
