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
Web apps using the Web Crypto API will only work in Secure contexts (HTTPS) (or for web apps served over localhost or .localhost domain)
The latest Keycloak release (26) began using this API in its Javascript adapter for example
How to bypass this limitation
In order to bypass this limitation and facilitate local testing using karate UI, we can add the following flag --unsafely-treat-insecure-origin-as-secure to chromium based browsers in karate docker images
Proposal
Add an optional environment variable in karate docker images that when set add its value as additional flags to browsers' startup command.
Why is this needed
Web apps using the Web Crypto API will only work in Secure contexts (HTTPS) (or for web apps served over
localhost
or.localhost
domain)The latest Keycloak release (26) began using this API in its Javascript adapter for example
How to bypass this limitation
In order to bypass this limitation and facilitate local testing using karate UI, we can add the following flag
--unsafely-treat-insecure-origin-as-secure
to chromium based browsers in karate docker imagesProposal
Add an optional environment variable in karate docker images that when set add its value as additional flags to browsers' startup command.
Using a generic environment variable should offer flexibility to adapt the images in future use cases
The text was updated successfully, but these errors were encountered: