---
# System prepended metadata

title: Solid Authorization Panel

---

# Solid Authorization Panel
December 2nd, 2020

## Present

- Emmet T
- Henry S
- Sarven C
- Justin B
- elf Pavlik
- Tom P

## Agenda

* ACP Updates (Emmet T)
* How to work on ACP
* Admin 
    * neutral Jitsi instance is proposed for all solid spec / panel meetings: https://gitter.im/solid/authentication-panel?at=5fc501ecba0b7a0fc53af86c
* PRs
    * Use case for client to discover access privileges: [PR 136](https://github.com/solid/authorization-panel/pull/136)
* Issues
    * List of WAC implementations [issue 139](https://github.com/solid/authorization-panel/issues/139)
    * WAC-Allow vs Link: rel="..." [issue 141](https://github.com/solid/authorization-panel/issues/141)
    * acp:apply* relations are confusing [issue 143](https://github.com/solid/authorization-panel/issues/143)
* From Pavlik - Discuss [OAuth is not User AUthorization](https://www.scottbrady91.com/OAuth/OAuth-is-Not-User-Authorization)

## Minutes

### ACP Updates

Emmet: Have updated documentation around logic of ACP evaluation. Section 4 has been updated:

(Operations are pseudo-typescript)
https://github.com/solid/authorization-panel/blob/master/proposals/acp/enforcement-propagation.md

Going into any of those now will have logic explained in
typescript with comments on relevant / important functions.

### https://github.com/solid/authorization-panel/issues/141

HT: Tension between WAC spec and ACP related to WAC-Allow

ET: Is meant to be a functional replacement for WAC-Allow

### https://github.com/solid/authorization-panel/issues/143

HS: Can this be simplified?

### https://github.com/solid/authorization-panel/issues/139

HS: Try to get / track down as many WAC implementations / implementors involved as possible

JB: Also should track down those who have created some custom authz systems when WAC was not sufficient and get roadblocks documented.




