Our first idea is about the types of users available. We'd like to
propose to have three main classes: administrator, user, guest. The
first two, are already incorporated in the design, but we also see
several potential usecases for the guest account. The main thing
different between standard user and a guest, is that the session data
would be immediately erased after log off. Also, potential access to
the guest account would be much easier and privileges much more limited.
If you look at the test image Tizen 3 Common you will see that the
concept of Guest is already there. Guest is a user which is connected
before login and has access to a restricted number of App.
We do not have a concept of an admin but rather the concept of privilege
users. Privilege users can administrate the systemn add and remove
global Apps.
Now, about the user creation process. This topic has been started a
while ago, but things got quiet and no agreement has been reached,
from my recollection. Generally we propose to add to GUMD a
possibility, for each package to install user management hooks. For
example:
1. A new user is created
2. A set of hooks is run
This feature is beneficial in regard to the upcoming containers
support in Tizen. We can't think of any other or better way to
propagate user management events to all the containers.
The use of GUMD was agreed by the architecture forum several month ago.
The code is in the Git tree and it should soon appears in Common.
If you need to add feature, the process is know :
- share your idea and need this list
- propose code
If the change is serious and use of container is, you will need to get
an OK from the architecture forum.
Regards
Dominig
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
