Repository navigation
Replies: 2 comments 11 replies
|
Hi, I run in to similar issue. Did you managed to resolve it or find a walkaround? |
|
Hi! Alternative options:
Or move to https. |
|
Using HTTPS in production is the only way to solve this, this is a limitation of user-agents we do not control. |
|
I have the same problem with our development enviroment using http and keycloak-angular like here: mauriciovigolo/keycloak-angular#626 |
|
found a workaround here (works on my ubuntu): https://stackoverflow.com/a/78397011/592737 |
|
Guess I may, just need to migrate multiple stacks which look similar to this one. I adopted # docker-compose.app.yml
name: kc-light
services:
keycloak:
networks:
kc-net-v1:
ipv4_address: 172.100.10.10
image: quay.io/keycloak/keycloak:26.4
environment:
HOSTNAME: auth.172.100.10.10.nip.io
static:
networks:
kc-net-v1:
ipv4_address: 172.100.10.20
environment:
HOSTNAME: static.172.100.10.20.nip.io
image: nginx:latest
api:
networks:
kc-net-v1:
ipv4_address: 172.100.10.30
environment:
HOSTNAME: api.172.100.10.30.nip.io
reactapp:
networks:
kc-net-v1:
ipv4_address: 172.100.10.50
environment:
HOSTNAME: app.172.100.10.50.nip.io
# more services / databases here
networks:
kc-net-v1:
driver: bridge
ipam:
driver: default
config:
- subnet: 172.100.10.0/24 |
|
This is definitely a solution but not really scalable for bigger companies. We have around 20 different frontends in development and most of them have test deployments used by many different customers daily to check new features. Getting them to setup a secure context seems much more difficult than actually implementing HTTPS. So all in all, this change in keycloak-js is a big nuisance to us. :/ |
|
Again, we don't control what web browsers decide to do, this is not a limitation of Keycloak JS. You can just secure your deployments with HTTPS, there is plenty of tooling to get that done. |
|
I admit I don't know about HTTPS and related topic to agree or disagree that (It's totally possible, of course, that in the same time span, our company's browsers all got updated to a version where HTTPS is expected and that it has nothing to do with the keycloak-js update I did.) |
|
It is literally not a limitation of Keycloak JS, but a well documented security feature of browsers. The only thing that has changed is that Keycloak JS now uses these APIs for cryptographically secure algorithms. |
Uh oh!
There was an error while loading. Please reload this page.
For the frontend React.tsx application, I use the KeycloakProvider wrapper (around App.tsx React), where I initialize keycloak-js (26.1.2) as follows: keycloak.init({onLoad: 'login-required', checkLoginIframe: false, pkceMethod: false}).
I need to run this application for the URL: http://our-local-network.internal/.
In the admin panel, in the Realm settings, I configure it like this: Require SSL of Realm: None, and in the public client settings for the frontend like this: Proof Key for Code Exchange Code Challenge Method: plain.
But! When navigating to the URL: http://our-local-network.internal/, there is an error in initializing keycloak.init, and I see the message: "Initialization error inside KeycloakProvider: Web Crypto API is not available".
In the development environment on localhost, everything works fine, but it doesn't work on HTTP.
This is my first time using a product like this, so please don't be too harsh.
Is there a guaranteed approach to fix this without using HTTPS?
Thanks in advance for your help!
All reactions