# 2020-06-15 Authentication Panel

## Agenda

* Dedicated AuthZ weekly call
* [Use Cases and Requirements](https://solid.github.io/data-interoperability-panel/use-cases-and-requirements/)
* auth-fetcher update
* Stable conferencing room
* Repo cleanup (open PRs and Issues)
* [Next week agenda](https://hackmd.io/FecpcyLkRWasZvoHtigftg)

## Present
* Aaron Coburn
* Dmitri Zagidulin
* Henry Story
* Jackson Morgan
* Ricky White
* Justin Bingham
* elf Pavlik

## Minutes

### Dedicated AuthZ weekly call

Last week session: [meeting notes]( https://github.com/solid/authorization-and-access-control-panel/blob/master/meetings/2020-06-10.md)

- Justin: At some point AuthZ merged with AuthN, possibly due to same group of people showing up to both meetings. I see it as different things that both require a lot of focus and attention. This focus should be consistent.
- ...: Last week we discussed the purpose and focus of AuthZ panel. Which initiatives it should focus on. I'm creating few issues today where we can work on that offline and get different perspectives. We should also align naming of repo and gitter channel to reflect focus of the panel. What do we really need to get done from priorities. For example we don't have normative Web Access Control spec. It has well documented gaps, Aaron shared a set of issues already. We also talked about various extensions like tagging, shapes client constraints etc.
- Jackson: I can commit to participate in both meetings.
- Justin: I've been joining AuthN to stay informed but AuthZ stays related more to work I've been doing.
- Aaron: The most important thing is focused meetings with clear agenda. Having separate meetings you can have right people at the right time. People can also read minutes if they don't participate, that's what I do.
- Dmitri: I see two issues inseparable. As AuthN calls get shorter it leaves more room for AuthZ topics. I can make two but would prefer one meeting.
- Justin: What if we would have them both bi-weekly and alternate on the same timeslot?
- Pavlik: I think if we have better organized work between meetings we may not need two meetings.
- Justin: Does anyone disagree with the bi-weekly schedule using the same timeslot?
- Aaron: If we don't have AuthN right we will have to be changing AuthZ. We should have more heavy push for AuthN right now.
- Justin: I'm worrying that nothing will hapen on AuthZ without regular meetings.

### Update on AuthN draft

- Ricky: we said we would provide 3 drafts to get to the first spec. This week we plan to provide a barebone MUST spec. If you don't start in that way it's easy to get convoluted.
- ...: It's up to you what form we give it to you. After the first draft we will have period to comment, make PRs and produce second draft.

### auth-fetcher update

- Jackson: We discuss splitting it into two libraries. Initially we wanted to launch it this week but we may push it back a little. If you want to work with new token curren version works with it. I've don't test with dev.inrupt.net and all seems to work with NSS version deployed there. NSS currently supports both token.
- Pavlik: Where NSS has the current support?
- Jackson: It has 4 PRs and I will merge them asap.

### Stable conferencing room

- Pavlik: Let's decide for Wednesday in issue.

### Repo cleanup (open PRs and Issues)

- Henry: We should clasify them. Sometimes we have good discussions but not relevant directly.
- Justin: We should clarify purpose of the panel and priority in initiatives.
- Ricky: Some issues are associated to Dmitri's draft. Do you want to create a new repo or do cleanup on this repo?
- Pavlik: What should we do with Dmitri's draft?
- Dmitri: We can archive it.
- Jackson: Should we just publish it even if we are not going to use it?
- ...: You have PRs nicely formated and gdoc with bunch of notes.
- Justin: Once we have draft from Ricky and Adam we should see previous conversations if they were addressed.
- Justin: We have github action setup that renders bikeshed, we can easily apply it to this repo.

## Action

- Ricky: make PR with initial draft in Markdown
- Justin: update wednesday AuthZ meeting time
- Pavlik: to follow up on all the issues with proposal how to close them