You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
SWA CLI default SSL certificate is wrong. SWA CLI provide --ssl option, but I can't access ssl site because SWA CLI certificate is not trusted. (fig.1)
And I get still error after trust SWA CLI localhost certificate. I guess SWA CLI certificate not have server auth OID (1.3.6.1.5.5.7.3.1) in EKU. (fig. 2)
Describe the solution you'd like
Add server/client auth to EKU of SWA CLI certificate like as ASP.NET Core localhost certificate.
Describe alternatives you've considered
Currentlly, I should use --ssl-key and --ssl-cert option with --ssl and own localhost certificate. (this is very troublesome.)
Additional context
fig.1
fig. 2
SWA CLI version: 2.0.1
OS: Windows 11 x64
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
SWA CLI default SSL certificate is wrong. SWA CLI provide
--ssl
option, but I can't access ssl site because SWA CLI certificate is not trusted. (fig.1)And I get still error after trust SWA CLI localhost certificate. I guess SWA CLI certificate not have server auth OID (1.3.6.1.5.5.7.3.1) in EKU. (fig. 2)
Describe the solution you'd like
Add server/client auth to EKU of SWA CLI certificate like as ASP.NET Core localhost certificate.
Describe alternatives you've considered
Currentlly, I should use
--ssl-key
and--ssl-cert
option with--ssl
and own localhost certificate. (this is very troublesome.)Additional context
fig.1
fig. 2
The text was updated successfully, but these errors were encountered: