Simeon Warner

Resolved. In Auth 2.0 the additional labels are defined only for the `active` interaction pattern: https://iiif.io/api/auth/2.0/#active-interaction-pattern

Closing this. Decision was not to address in Auth 2.0 that provides for auth only on Content Resources, see https://github.com/IIIF/api/issues/1890 for the use case that would add coverage of IIIF...

Resolved with publication of Auth 2.0. The IP address scenario is highlighted as one possible authorizing aspect, see e.g. https://iiif.io/api/auth/2.0/#terminology

Was typo for "date-only" I think, have corrected above

Resolved with publication of Auth 2.0 https://iiif.io/api/auth/2.0/. The approach is now resource (URI) centric and there is more uniform description of different access controlled resources, without any mention of the...

Resolved. The IIIF Authorization Flow 2.0.0 specification was published 2023-06-02: https://iiif.io/api/search/2.0/

Resolved in Auth 2.0, see `expiredAspect` in https://iiif.io/api/auth/2.0/#access-token-error-format

Resolved. We decided not to create Auth 1.0.1. The word "appropriated" does not appear in Auth 2.0 https://iiif.io/api/auth/2.0/

IMO Auth 1 and Auth 2 are sufficiently different that it would probably be best to have two separate implementations in code that would want to support both. Suggest "close,...

Resolved with publication of Auth 2.0 https://iiif.io/api/auth/2.0/ . With the introduction of the probe service we are no longer directly using HTTP response codes as the means to understand access...