• privileges, a generic model
  • group, role and role hierarchies, draft proposal for MACE-wide model and definition
    • Are the definitions in the glossary good enough or are their others that are more widely accepted?
      • mace documents ( grouper)  vs other standards groups
  • Using groups and roles vs privileges, how to choose,  simple access management, centralized vs distributed.  Note: you can mix and match between these strategies in one application
    • You can centralize your groups/roles/privileges to take advantage of shared middleware, or to be able to centrally query/change authorizations, or to reuse the authorization settings across multiple applications
    • If you are hardcoding privileges in applications based on group, then you can have groups that hold the subjects allowed to do those things.  For example, you might have a group of timesheetUsers, and a group of timesheetAdmins, and in the application in the code you can see if the user is a timesheetAdmin and allow more features for that user
    • If you want to dynamically assign what a group is allowed to do, then you should use a role, externalize the privilege resources from the code, and assign those privilege resources to the role.  This role can be assigned to individual users or to groups of users.  Role based access control is useful in parts of your application where groups of users have the same privileges.
    • For parts of your application where users' privileges do not generally overlap with other users' privileges, you can assign privileges directly to the user
  • How much can access management be centralized vs embedded in applications?
  • Follow the attributes
  • Are their really use cases when access requires realtime evaluation or is static evaluation or cached evaluations enough?
    • Use cases using "presence detection" , is this person physically in a building  or a room
    • Use cases with quota evaluation, metering or rate limiting a for fee service?
  • case studies
• attribute delivery recipe:
  • SAML between IdP & SP
  • SPML, XMPP ( grouper) for push provisioning
    • XMPP is a messaging protocol that many institutions already run with known security and addressing standards
      • JMS or activeMQ ? AMQP as a wire protocol.
  • LDAP , privilege registry or webservice   for pull provisioning
    • is there existing mace-dir work to build on?
• generalizing to federated scenarios and VOs
  • What is the namespace  ( URIs vs  URNs) and object characteristics for privileges
    • what are the special problems in namespace choice?
      • The name/meaning of a privilege may reflect the policy intention of an organization or a virtual organization and may be applied to subset of either.
      • Some architectures take the "CRUD" view where everything is mapped to create, read, update, delete on specific objects
      • Some architectures use privilege names scoped to the  resources they reference.
      • examples
        • urn:mace:cmu.edu:andrew:s3:field:ssn=read
        • urn:mace:cmu.edu:andrew:s3:canreadssns
        • http://www.cmu.edu/andrew/s3/fields/ssn/read
      • The actual privilege may be represented differently by the policy enforcement points in an application or service or may be represented in multiple application for services
      •  
    • Fifer using URIs
• authorization and access control
  • case studies in production
• rule-based access control
  • XACML , DROOLS, others
• policy, a generic model
  • P*P architectures: proposed models,
    • Application policy, enterprise policy, VO policy
  • case studies - bamboo

examples of access management in production

• • performance issues and design tradeoffs
• Experience with commercial and open source offerings
  • The Aegis Identity Management Suite based on open standards tools