![How to Build an AI Assistant with Keith Moehring [MAICON 2025 Speaker Series]](https://www.marketingaiinstitute.com/hubfs/MAICON-Speaker_Series%20%281%29.png)
![[The AI Show Episode 156]: AI Answers - Data Privacy, AI Roadmaps, Regulated Industries, Selling AI to the C-Suite & Change Management](https://www.marketingaiinstitute.com/hubfs/ep%20156%20cover.png)
![[The AI Show Episode 155]: The New Jobs AI Will Create, Amazon CEO: AI Will Cut Jobs, Your Brain on ChatGPT, Possible OpenAI-Microsoft Breakup & Veo 3 IP Issues](https://www.marketingaiinstitute.com/hubfs/ep%20155%20cover.png)
![Rust VS Go VS TypeScript – which back end language is for you? With Tai Groot [Podcast #176]](https://cdn.hashnode.com/res/hashnode/image/upload/v1750974265013/73f79068-0087-4c39-8a8b-feea8cac873b.png?#)
.jpg?width=1920&height=1920&fit=bounds&quality=70&format=jpg&auto=webp#)
Desktop application with role-based access [closed]
I am developing an application in java (swing) which requires authentication. The application behaviour needs to change depending on the role of the user. These changes might be "complex": consider a tree (maybe representing a file system) such that, based on the role of the authenticated user, the expansion of some node is forbidden. The authentication is based on a local DB which will be most likely used for the roles as well. How would you implement these changes in behaviour? Some ideas are: roles kept as an enum and behaviour determined by switch cases interface-based developement with the FQN of the implementing classes saved on DB: each role implements a component differently and this implementation can be retrieved by the name of the class saved on DB.
I am developing an application in java (swing) which requires authentication. The application behaviour needs to change depending on the role of the user. These changes might be "complex": consider a tree (maybe representing a file system) such that, based on the role of the authenticated user, the expansion of some node is forbidden.
The authentication is based on a local DB which will be most likely used for the roles as well.
How would you implement these changes in behaviour?
Some ideas are:
- roles kept as an enum and behaviour determined by switch cases
- interface-based developement with the FQN of the implementing classes saved on DB: each role implements a component differently and this implementation can be retrieved by the name of the class saved on DB.
