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

Reverse the relation between django users and managing authorities (how should we manage access control on jites functionalities) #12

Open
franchg opened this issue May 7, 2013 · 2 comments

Comments

@franchg
Copy link
Contributor

franchg commented May 7, 2013

As discussed with @droghetti we probably need to put a nullable FK on django users table thowards managing authority, reversing the current relation. Another idea is to assign a special group to managing authorities, maybe it's easier and cleaner?
Please let's elaborate on this topic and how we are going to manage security of various functionalities of the software.

  • Should django be aware of managing authorities?
  • Does this help us to secure the system?
@ghost ghost assigned ernestoarbitrio May 7, 2013
@ernestoarbitrio
Copy link
Contributor

i thinks that, instead of changing the auth django models, we can use a group for managing authority and change the fk on the ma table to the auth_group of django.
In this way we can have:

  1. Group Piemonte Authority (user1, user2, ..... userN)
    and link the group to the MA.

Comments welcome!

@franchg
Copy link
Contributor Author

franchg commented May 27, 2013

Implemented and committed in db, I've removed the FK to django tables

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants