-
-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Access Profile, User and Cards #46
Comments
xaqq
added a commit
that referenced
this issue
Nov 25, 2014
We can now tie a user to multiple groups. Permissions are gathered from all groups and we compute a profile using this. Caveat: Single user permissions and group permissions don't play well together (yet). This is work in progress toware #46.
Multi group are supported for one user. |
xaqq
added a commit
that referenced
this issue
Nov 25, 2014
Temporary access cards are postponed until later. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implements base code to handle "Access Profile". A profile
holds the base configuration information about whether or not a user
will be granted access.
The profile control which days / hours the user has access. It also
controls what door the user has access to.
A user can have multiple access card, but only one access profile.
An access card maps to a user. The user's profile is then used to
grant or deny access.
Temporary access card also exists. Those maps directly to access profile.
A group can map to an access profile.
A user can be part of a group. If the user has a specific access
profile, his group profile shall be ignored.
This looks like this:
This is related to authentications modules: mapping will vary (LDAP
backend to map user to group, SQL backend that holds acess profile
info, group membership, etc).
The control code should be reusable once the proper access profile,
group, user, and cards are correctly mapped.
The text was updated successfully, but these errors were encountered: