Skip to content

Instantly share code, notes, and snippets.

@AdamBien
Created June 4, 2020 09:25
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save AdamBien/ed9b266efa084a74864b0e9f5512f29c to your computer and use it in GitHub Desktop.
Save AdamBien/ed9b266efa084a74864b0e9f5512f29c to your computer and use it in GitHub Desktop.
76thAirhacksQ&A.md

Ask questions and see you at July, 6th, 8.PM. CET: https://vimeo.com/415639656

Also checkout recent episode:

75th airhacks.tv

Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions.

@szymonk92
Copy link

Hi Adam,

In my project, we use pretty complicated Access Policy which for every entity has a user and group rights. Groups might be predefined as well as created by the administrator user. So for every entity user or group (or both) can have READ/WRITE/OWNER rights. This approach requires 2 additional tables for every entity (+additional 2 for Envers) and has multiple joins. Do you know any better way to manage rights for entities? I was wondering if we could use KeyCloak to help us with that, however not sure if we can use User and Groups policies together. What's your opinion on that?

Thanks
Szymon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment