Replies: 2 comments
-
Thanks for bringing this up @vramik. From HotRod point of view, there is no problem with it. I actually did the same thing when started work on HotRod authz implementation. The problem may be tree store configuration as if I understand correctly, we are now able to configure different tree/node configurations for each authz sub-area. But if we decide we want only one configuration for the whole authz, this change could be ok. |
Beta Was this translation helpful? Give feedback.
-
There are stores stored in CHM based on the names: https://github.com/keycloak/keycloak/blob/main/model/map/src/main/java/org/keycloak/models/map/storage/chm/ConcurrentHashMapStorageProviderFactory.java#L97 To make it work we'd need to change CHM implementation to something like Therefore we've decided we'll park it for now and adjust it only in jpa implementation, similarly as it is in HotRod currently. |
Beta Was this translation helpful? Give feedback.
-
I'd like to get confirmation there is no plan to support different stores for each authz object (
Permission
,Scope
,ResourceServer
, ...) in future. AFAIK there is not, but I want to be sure.When implementing jpa-map-storage for authz I've encountered following code in
ModelEntityUtil.MODEL_TO_NAME
I'd like to have all changelogs for all of them into single one so I was wonding if we should/could change
ModelEntityUtil.MODEL_TO_NAME
following way:Would it break something? I can workaround it in the jpa implementation if there is an issue with it.
Beta Was this translation helpful? Give feedback.
All reactions