Already for the MVP we could add a collection user-profiles,
where for each user a profile document is inserted.
-
A UserProfile model class needs to be defined @Documententity class containing
- UserId => to access the email
- name
(- profile specific actions as Rules, Config (to be specified and implemented in another issue, I suggest)
-
A default profile needs to be created and inserted on registration => done by the RegisterService
-
The ExampleInitializer has to create profiles for the test user(s)
-
The registration form should get another input field for name
-
an endpoint to retrieve the UserProfile (for the default user taken from Principal - no userid parameter)
Rational: That gives as first step the opportunity to greet a logged in user with correct name.
In a later step many rules or configurations can be stored in the profile.
Already for the MVP we could add a collection
user-profiles,where for each user a profile document is inserted.
A UserProfile model class needs to be defined
@Documententity class containing(- profile specific actions as Rules, Config (to be specified and implemented in another issue, I suggest)
A default profile needs to be created and inserted on registration => done by the RegisterService
The ExampleInitializer has to create profiles for the test user(s)
The registration form should get another input field for name
an endpoint to retrieve the UserProfile (for the default user taken from Principal - no userid parameter)
Rational: That gives as first step the opportunity to greet a logged in user with correct name.
In a later step many rules or configurations can be stored in the profile.