# WG Meeting: 2023-03-07
## Agenda
- [Atul] Review [open issues](https://github.com/openid/sharedsignals/issues)
- [Atul] Discuss making jwks_uri optional ([Open Issue #44](https://github.com/openid/sharedsignals/issues/44))
- [Atul] Create stream issues ([#45](https://github.com/openid/sharedsignals/issues/45) and [#46](https://github.com/openid/sharedsignals/issues/46))

## Attendees
- Atul Tulshibagwale (SGNL)
- Debora Comparin (Thales)
- Eric Karlinsky (Okta)
- Greg Brown (Axiad)
- Peter Travers (Beyond Identity)
- Shayne Miel (Cisco)
- Topher Marie (Strata)
- Tim Cappalli (Microsoft)

## Notes
### JWKS URI (#44)
- Do SSF JWTs need to be signed? Current understanding is that they don't need to be signed if sent on an integrity protected transport like TLS
- Can we make the jwks_uri field in the Transmitter Configuration Metadata optional? Yes, [Eric], no objections

### Create Stream Issues (#45)
- Discovering "events_supported" before creating a stream:
- Requirement seems real, we can alter the response to pull "events_supported" out of each stream's configuration
- We could add a separate endpoint to get the events supported
- Separate endpoint is the preferred option in the call (Shayne, Tim and Peter). The endpoint couldbe called "get events supported"
- We should not remove the "events_supported" field from the existing response to "get stream configuration" because the events supported may be different per stream
- We should not have a "stream id" parameter to the new endpoint to "get supported events"

### Create Stream Issue (#46)
- Continue discussion next time

## Action Items