Opened 15 years ago

Closed 14 years ago

#3 closed enhancement (fixed)

Use Moira-fed sources for authorization

Reported by: adehnert Owned by:
Priority: normal Milestone: Initial Release
Component: Core Version:
Keywords: Cc:
Size:

Description

Letting people use blanche and similar tools for managing authorization is shiny. The DB should possibly use a Moira-fed source (Moira itself, AFS groups, or LDAP) for checking for authorization.

Change History (6)

comment:1 Changed 15 years ago by adehnert

  • Milestone set to Initial Release

comment:2 Changed 14 years ago by adehnert

  • Component set to Default

This is probably not going to happen for group signatories.

For things like ASA EBM, this should absolutely happen.

comment:3 Changed 14 years ago by adehnert

  • Component changed from Default to Core

Relevant lists for CAC access:

  • student workers: cacstudentworkers
  • staff: cacstaff

(See https://diswww.mit.edu/menelaus/asa-db/443.)

comment:4 Changed 14 years ago by adehnert

Current intent is that the lists on asa-db-sync-lists will be used for syncing. (Mostly not directly lists from individual offices, because asa-db-mit-{deskworker,offices} will probably need multiple sublists, and sao-internal is hidden, so it'll need a wrapper of to make it visible.

comment:5 Changed 14 years ago by adehnert

Commit ac1d8975674184bf1084bf8386697e2781c0d665 and its immediate predecessors make this work for Django group membership. Unfortunately, they don't handle the "staff" flag at the moment. (Also, they cause adehnert-admin to get punted from asa-ebm. Ah well.)

comment:6 Changed 14 years ago by adehnert

  • Resolution set to fixed
  • Status changed from new to closed

Staff status is fixed in:

commit c8cb9baab284bd45e84140c69599261f53887f7b
Author: Alex Dehnert <adehnert@mit.edu>
Date:   Fri Dec 23 00:00:02 2011 -0500

    Sync staff status with the asa-admin list as well

    It's possible we actually want to have some whitelist of "people who should
    always have staff status". Not clearly worthwhile enough for me to implement
    something now, though.

I think that's all we need.

Note: See TracTickets for help on using tickets.