Skip to Content.
Sympa Menu

technical-discuss - RE: [InC-Technical] default attribute release policy

Subject: InCommon Technical Discussions

List archive

RE: [InC-Technical] default attribute release policy


Chronological Thread 
  • From: "Cantor, Scott" <>
  • To: Roland Hedberg <>
  • Cc: Tom Scavo <>, Scott Koranda <>, "" <>
  • Subject: RE: [InC-Technical] default attribute release policy
  • Date: Thu, 8 Jun 2017 19:19:25 +0000
  • Accept-language: en-US
  • Authentication-results: spf=pass (sender IP is 128.146.138.11) smtp.mailfrom=osu.edu; gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=pass action=none header.from=osu.edu;
  • Ironport-phdr: 9a23:GJ5GaxxGpBmTmbXXCy+O+j09IxM/srCxBDY+r6Qd2ukeIJqq85mqBkHD//Il1AaPBtSErawfwLON7+jJYi8p2d65qncMcZhBBVcuqP49uEgeOvODElDxN/XwbiY3T4xoXV5h+GynYwAOQJ6tL1LdrWev4jEMBx7xKRR6JvjvGo7Vks+7y/2+94fdbghMhjexe7J/IRu5oQnMuMQbjpZpJ7osxBfOvnZGYfldy3lyJVKUkRb858Ow84Bm/i9Npf8v9NNOXLvjcaggQrNWEDopM2Yu5M32rhbDVheA5mEdUmoNjBVFBRXO4QzgUZfwtiv6sfd92DWfMMbrQ704RSiu4qF2QxLzliwJKyA2/33WisxojaJUvhShpwBkw4XJZI2ZLedycr/Bcd8fQ2dKQ8RfWDFbAo6kb4UBEfcPPfpWoYf+qVsBrxq+ChWjCuzg0TJImmT50Kkm3+g9DQ3L3gotFM8OvnTOq9X1Mb8fXe6rwabSyzXDc/RW2S3l5IPVbx4uvfaMXa5sccbf1EIiEB/KgU+WqYz5ODOVzP4Bv3aA4upnTuKvlnQrpB9srTiy38ohjJTCiIENyl3c6Cl13Ik4Kce3RUN5e9KpHplduzuHO4Z4Xs8uW3xktSc1x7EcpJK3YCoHxI45yxPQafGLaZWE7xPtWeqJLzd3mnFodK66ihu3/0WtzuzxWtWx3VlXsyVIkdjBu3UW2BPJ9MSKT+Fy8Vq/1TuO0Q3Y9/tKLloulaXBLp4s2r4wmYQXsUTEBiL4gFn7gqiKekk64+Sl9ebobqj/qp+bLIB7lBvyMqMzmsyjGus4NRUOX26G9uimzL3j50r5QKlUgfIqjqnZsZfaJcIBqq6+Hg9VzoIj6xG4DzelytgXgX4HLFdddBKGiYjmJU3OLejlAfujjFmgijhmyvLcMrDvAJjBNGXPnbn9cbpl7k5T0gszzdRR55JODbEBJer+VVPru9zeEh85NBa0z/z5BNhm0YMeQn+PDrWHP6zPrF+E/vgvLPWUZI8JpDb9LOAo5//ojXAlnl8deKyp3ZwRaHyiGfRmOUqZbWPwgtgfDWgKvgw+TO32h1KYVT5ffmu9X6Mn5j4nFYKmFpzDS5upgLyAxye7AoZWan5cBlCNF3foa5uLW+0KaC2MPs9tjCYIWqa8RI88hlmSs1rAzL5uKOac2iAUv5/525Ah/erXnBc+3SdpCcmBlXqAGTJahGQNEnUd1aZjplY5gmyI1rRkybQMHtVV+/RTFF0SMoXBieF2FoahCUr6Yt6VRQP+EZ2dCjYrQ4d0modWbg==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

> A SP/RP can in the client registration specify that it wants pairwise and
> not
> public identifiers.

That amounts to burying the signaling out of band, which I think is silly.
Either approach works, but if you don't start out with a single attribute, I
don't think it's advantageous to go there after the fact. But I also don't
care that strongly either. I said on the last deployment WG call that if
there was real consensus for copying OIDC and using eduPersonUniqueID for
both cases I'd live with it, it's not a hill I care to die on.

-- Scott




Archive powered by MHonArc 2.6.19.

Top of Page