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
I've imported a self-signed cert for my local (intranet) web server into my windows certificate store and also imported it into the 'servers' section of the Options => Advanced => Certificates of the Firefox running in the context of the currently logged in user, however when I launch the Firefox via karma it seems to run in a brand new/temporary Firefox user profile and all my manual steps seem to have no effect - i.e. test fails due to
myhost.foo.bar.com:7443 uses an invalid security certificate. The certificate is not trusted because it is self-signed. (Error code: sec_error_unknown_issuer)
Tips/suggestions welcome - I couldn't find anything from quick googling on how to tell Karma to launch Firefox using a specific user profile or using specific set of 'permanent' exceptions that have been configured...
The text was updated successfully, but these errors were encountered:
Pre-import the cert into an existing profile and distribute the cert.db file source.
It's also mentioned in the official doc, but they recommend against it. For testing purposes it seems like it would be sufficient.
hi,
I've imported a self-signed cert for my local (intranet) web server into my windows certificate store and also imported it into the 'servers' section of the Options => Advanced => Certificates of the Firefox running in the context of the currently logged in user, however when I launch the Firefox via karma it seems to run in a brand new/temporary Firefox user profile and all my manual steps seem to have no effect - i.e. test fails due to
myhost.foo.bar.com:7443 uses an invalid security certificate. The certificate is not trusted because it is self-signed. (Error code: sec_error_unknown_issuer)
Tips/suggestions welcome - I couldn't find anything from quick googling on how to tell Karma to launch Firefox using a specific user profile or using specific set of 'permanent' exceptions that have been configured...
The text was updated successfully, but these errors were encountered: