You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
We need to come up with a concept what user related data (or application related data being more general) should be kept in the client. Example pieces of such data are:
user name, date / time format, language
dialogs the user is authorized for
user's menu structure
Needed are the following steps:
Server-Side (Java):
Implement a transformer which based on the current user information creates a data structure holding the data needed in the client. The data structure is returned by the SecurityRestServiceImpl.getCurrentUser() REST service.
Client-Side (JavaScript):
update the appContext service accordingly
The text was updated successfully, but these errors were encountered:
We already have user name (first and last name). Already provided by the service.
For data/time and language my question is: Would it not be sufficient in our sample app to use the HTTP and browser standard for this? You can determine the locale of the current user. To switch locale you then have to change it globally in your OS. This might be undesired but I consider this as a rather advanced use-case. With lower priority we can implement this so the defaults apply but the user has the chance to override via his profile.
In our sample we have a simple role base concept. This is IMHO totally sufficient here. The role already contains all information required. Find an arbitrary way to figure out what you need to know based on the role of the user within jsclient.
I disagree on this. We should keep the sample application simple. Personalized menu structures are a very special use-case. Do not lead our projects to overcomplicated solutions.
OK, so let keep it simple. We need a simple authorization component which would map the roles (obtained from the server) to dialogs. The component can then be used to:
render a menu
checking if a given dialog is to be shown or not
(just examples, not a complete list).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need to come up with a concept what user related data (or application related data being more general) should be kept in the client. Example pieces of such data are:
Needed are the following steps:
Server-Side (Java):
Implement a transformer which based on the current user information creates a data structure holding the data needed in the client. The data structure is returned by the SecurityRestServiceImpl.getCurrentUser() REST service.
Client-Side (JavaScript):
update the appContext service accordingly
The text was updated successfully, but these errors were encountered: