...
For more information about the working group, please see the OIDC Survey Working Group Home wiki space.
Change Proposals and Feedback - We welcome your feedback/suggestions here
If you have comments that do not lend themselves well to the tabular format below, please create a new Google doc and link to it in the suggestion section belowFinal Revised OIDC Working Group Report is here (April 2017).
Number | Current Text | Proposed Text / Query / Suggestion | Proposer | +1 (add your name here if you agree with the proposal) | Action (please leave this column blank) |
|---|---|---|---|---|---|
| 1 | Throughout section 6.1 | Planning to add OIDC/OAuth protocol to existing products is warranted but more attention should probably be given at outset to importance of an Authorization Server capability. There seems to be a large gap between, on the one hand - Shib's current responsibility for authentication; Grouper's responsibility for group management - and, on the other, the need for an OIDC/OAuth-responsive infrastructure that has a fairly deep awareness of both the use case variants outlined and authorization claims at the level of business applications. | B. Savage | The OIDC survey group doesn't want to be overly prescriptive of what the TIER project should do. We have, however, added Authorization Server as an example of other services that should be considered for the TIER strategy. | |
| 2 | |||||
...