Skip to content
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

Closed
xaqq opened this issue Nov 3, 2014 · 2 comments
Closed

Access Profile, User and Cards #46

xaqq opened this issue Nov 3, 2014 · 2 comments
Assignees
Labels
Milestone

Comments

@xaqq
Copy link
Contributor

xaqq commented Nov 3, 2014

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:

             Profile <------ user <------ cards
                       <------ temporary cards.
                       <------ group <----- user

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.

@xaqq xaqq added the feature label Nov 3, 2014
@xaqq xaqq self-assigned this Nov 3, 2014
@Maxhy Maxhy added this to the 0.4 milestone Nov 17, 2014
xaqq added a commit that referenced this issue Nov 24, 2014
This commit update message passing spec (#47) and update
implementation to follow thoses.

It also provide simple (but working) auth rules using configurable
by date (groups are not available yet). This is basic implementation
of #46.
xaqq added a commit that referenced this issue Nov 25, 2014
This commit update message passing spec (#47) and update
implementation to follow thoses.

It also provide simple (but working) auth rules using configurable
by date (groups are not available yet). This is basic implementation
of #46.
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.
@xaqq
Copy link
Contributor Author

xaqq commented Nov 25, 2014

Multi group are supported for one user.
Single user permissions + group permissions arent yet.

xaqq added a commit that referenced this issue Nov 25, 2014
@xaqq
Copy link
Contributor Author

xaqq commented Dec 10, 2014

Temporary access cards are postponed until later.
Groups and user permissions works.

@xaqq xaqq closed this as completed Dec 10, 2014
xaqq added a commit that referenced this issue Aug 19, 2016
This commit update message passing spec (#47) and update
implementation to follow thoses.

It also provide simple (but working) auth rules using configurable
by date (groups are not available yet). This is basic implementation
of #46.


Former-commit-id: c3f0def
Former-commit-id: 98ac58b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants