Indicates who took minutes -
ReadyTalk:
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free:
  - http://www.readytalk.com/intl
  - Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
  - Once on the call, enter participant code 2257295
IRC:
- Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #duraspace-ff on irc.freenode.net

Agenda

Minutes

...

PEP can be made effective
- ensure correct response codes
- early work on filtering search/triplestore results
- mock PEP
First cut, store policies within f4
Goal
- Three users, three rights r/w, r-o, no-access
Two questions
1. What permissions does this principal have?
2. What can I do?

Panel

title	Short-term Goals

Define a Policy Enforcement Point (PEP) interface (done)
Make sure Fedora REST calls honor PEP decisions with proper response codes (via mocked or stubbed PEP implementation) (in progress)
Create a simple ACL model for persistence on Fedora objects. (with read, write and acl-write/admin roles assigned to usernames)
Create and test a simple, non-XACML PEP that is driven by this ACL.

Help welcomed with the following:

Creating an extension point for retrieving user details and marshaling these into security principals we can serialize as strings (for ACLs). (E.g. LDAP groups, named IP ranges (On Campus), age, whatever)
Outline app developer needs with regards to no-op security checks
Outline app developer security needs for UI development generally
More thoughts on what we can do to support PEPs that delegate to external PDPs.