Apoorva Deshpande

We have defined the use of OAuth 2.0 as an authorization scheme in our interoperability draft. This PR adds more details about using OAuth constructs to make vendor interoperability more...

Transmitter needs ability to dictate what data it wants to share

4

Currently the spec has "add_subject", "remove_subject" as optional operations that are driven by the receiver. With these operations the receiver decides which subjects should be (or shouldn't be) part of...

[CAEP] device management change is not captured in the existing events

3

In the world of device management, the device management signal is very important. It does not directly map to the device compliance status. Device compliance status could be the result...

IP Addresses as a format Closes #201

New CAEP event - Risk level change event Closes #200 Removed `ips` claim from the event and created #201 to handle it separately for all CAEP events

A list of IPs as a new subject member in SSF

3

As we are seeing the need for communicating IPs in more events, this issue proposes a list of IPs as a new [Complex Subject Member](https://openid.github.io/sharedsignals/openid-sharedsignals-framework-1_0.html#name-complex-subject-members) member. The following events have...

New event to represent risk level changes

3

### Context A software vendor may deploy mechanisms to gather and analyze various signals associated with subjects such as users, devices, etc. These signals, which can originate from diverse channels...

Update error table

8

A follow-up from https://github.com/openid/sharedsignals/pull/247 @jischr please take a look