Please check my website

https://makirshpuzzle.com/
[https://makirshpuzzle.com/static/images/makirshpuzzle.com.png]<https://makirshpuzzle.com/>
Free game for your PC, Android, and iPhone - 
MakirshPuzzle<https://makirshpuzzle.com/>
MAKirsh Puzzle is gaming site with collection of more than 16000 games. You can 
play games on your laptop, desktop, android, and iPhone for free.
makirshpuzzle.com



Thanks,


________________________________
From: Thai Le <lnthai2...@gmail.com>
Sent: 25 October 2021 23:00
To: users@activemq.apache.org <users@activemq.apache.org>
Subject: Keycloak confidential access type for Artemis admin console

Hello,

In the security-keycloak example, the client artemis-console defined in
keycloak is set to be public access and thus keycloak-bearer-token.json has
no client secret. Does it mean the web console is entirely client side
javascript app ? If yes then how does it store the refresh token?

Just a bit of context, I am only interested in securing the artemis web
console with KC, not the broker (activemq realm) thus i am not configuring
the keycloak-direct-access.json. I want to be sure that the web console
does not call an endpoint on the broker to get the refresh token.

Regards

Thai Le

Reply via email to