Skip to content

Latest commit

 

History

History
80 lines (73 loc) · 3.3 KB

2021-06-02.md

File metadata and controls

80 lines (73 loc) · 3.3 KB

SCIM IG Meeting Notes - 06-02-2021

Attendees

  • Phil Hunt
  • Wes Dunnington
  • Matt Domsch
  • Paul Lanzi
  • Danny Mayer
  • Kevin Kampman
  • Jacob Childress
  • Anjana Samindra
  • Kevin K. Kampman
  • Matt Peterson
  • Tim Cappalli

Agenda

  • Go through the interest chart for existing and

Notes

  • these meetings ARE under the terms of "Note Well"

  • What is a BOF anyway

    • Demonstration to Area Director and IETF mgmt that there is a reason and that there are adults in the room
  • On the paging draft

    • there are cool new features in the paging draft such as selecting subsets of multi-valued attributes
    • you could have millions of values in a JSON doc, for example a large group
    • Ideally the goal would be to minimize the return
    • EG: entitlements, where you are searching for a 2ndary attribute
  • Phil: SCIM was created as a provisioning protocol, not a directory and as such, User Interfaces were out of scope - but people do it all the time

  • Phil: possible best practices document: mapping best practices for writing robust RESTful SCIM client code

    • eg: client tries to assert long id, server forces simple
    • what to do?
  • Topic: sub-attributes (metadata for attributes)

    • Date created, last modified etc
    • Kevin: Possible angle around signed attributes/blockchain?
    • Possible future debate??
  • Phil: HTTP Conditionals

  • Points on the Interest List

    • Triggers and Events
      • Pam: are there better places?
      • Matt: issue is around client-side caching - customers want it
        • Phil: this is a prime use case for conditionals but it is a polling solution unfortunately
      • Tim: in the development of SSE, an effort was made to be an "in-session" framework rather than a way to push SCIM data
      • Matt: there are already frameworks where a changed event emits notifications (that way they are idempotent)
  • Talking about the List in Order:

    • Multi-value Filtering/Paging
      • Matt: Why were entitlements never a first-class resource?
  • Interest:

    • Multi-value filter/paging: check
    • Cursor pagination (*): could be smaller support
      • folks in original group had concerns over DOS potential
      • from client perspective, need a way to sync the data
    • Relying Party User Provisioning: check
    • Soft Delete: check
    • PAM Schema (*):
      • concepts outdated, draft needs to be revisited
      • value in idea but
    • New HR Schema (new)(*) *
    • Schema Work
      • HR
      • Research & Education
      • Enterprise "Group" Schema
        • Today group doesn't have schema

Actions:

* Pam and Matt to