You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no user interaction before opening the access cookie service URI, and therefore any of the label, header, description and confirmLabel properties are ignored if present.
The JSON examples have label and the other recommended but ignored properties. What's the point of making label required (and the others recommended) if the clients are instructed to ignore it/them?
@id for instance has a description that prescribes use for particular types of services: It is required with the Login, Clickthrough, or Kiosk patterns, in which the client opens the URI in order to obtain an access cookie.
The text was updated successfully, but these errors were encountered:
From @ksclarke in Slack:
From the properties table at https://iiif.io/api/auth/1.0/#service-description it looks like label is required. But once one gets down to the Kiosk and External patterns we see:
The JSON examples have label and the other recommended but ignored properties. What's the point of making label required (and the others recommended) if the clients are instructed to ignore it/them?
@id
for instance has a description that prescribes use for particular types of services: It is required with the Login, Clickthrough, or Kiosk patterns, in which the client opens the URI in order to obtain an access cookie.The text was updated successfully, but these errors were encountered: