Events without label "editorial"
Issues
------
* oauth-wg/oauth-identity-chaining (+1/-0/💬0)
1 issues created:
- Standards Track vs. Informational (by bc-pi)
https://github.com/oauth-wg/oauth-identity-chaining/issues/175
* oauth-wg/oauth-transaction-tokens (+3/-11/💬19)
3 issues created:
- Clarify request_context normative language (by PieterKas)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/268
- PineSoeLin (by pinesoelin6-lab)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/267
- 0182874576 (by pinesoelin6-lab)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/266
14 issues received 19 new comments:
- #268 Clarify request_context normative language (1 by PieterKas)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/268
- #236 WGLC Editorial comments from Dan Moore (2 by PieterKas, tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/236 [WGLC Feedback]
- #234 TTS Configuration (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/234 [WGLC Feedback]
- #232 Need consistent normative language for txn claim (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/232 [WGLC Feedback]
- #226 Clarify "determining" (2 by PieterKas, tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/226 [WGLC Feedback]
- #223 Clarify Example (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/223 [help wanted] [WGLC Feedback]
- #222 Should tctx field be a MUST (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/222 [WGLC Feedback]
- #221 Clarify difference between sub and req_wl (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/221 [WGLC Feedback]
- #220 Clarify aud claim (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/220 [WGLC Feedback]
- #216 txn-ctx modification (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/216 [WGLC Feedback] [WGLC Discuss]
- #213 Compare WIMSE arch doc terminology with Transaction token spec (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/213 [help wanted] [WGLC Feedback]
- #197 Clarify request_details (1 by tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/197 [help wanted] [WGLC Feedback]
- #196 BASE64URL Parameter Encoding (4 by PieterKas, gffletch, tulshi)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/196 [WGLC Feedback]
- #180 Is subject_token always Base64 URL format? (1 by PieterKas)
https://github.com/oauth-wg/oauth-transaction-tokens/issues/180
11 issues closed:
- PineSoeLin https://github.com/oauth-wg/oauth-transaction-tokens/issues/267
- 0182874576 https://github.com/oauth-wg/oauth-transaction-tokens/issues/266
- Intended status: informational https://github.com/oauth-wg/oauth-transaction-tokens/issues/169
- Clarify claim usage https://github.com/oauth-wg/oauth-transaction-tokens/issues/228 [WGLC Feedback]
- Extend life of transaction tokens https://github.com/oauth-wg/oauth-transaction-tokens/issues/211 [WGLC Feedback]
- Reference WIMSE WIT https://github.com/oauth-wg/oauth-transaction-tokens/issues/218 [WGLC Feedback]
- Clarify aud claim https://github.com/oauth-wg/oauth-transaction-tokens/issues/220 [WGLC Feedback]
- Clarify difference between sub and req_wl https://github.com/oauth-wg/oauth-transaction-tokens/issues/221 [WGLC Feedback]
- TTS Configuration https://github.com/oauth-wg/oauth-transaction-tokens/issues/234 [WGLC Feedback]
- Describe parameter use https://github.com/oauth-wg/oauth-transaction-tokens/issues/231 [WGLC Feedback]
- Need consistent normative language for txn claim https://github.com/oauth-wg/oauth-transaction-tokens/issues/232 [WGLC Feedback]
* oauth-wg/oauth-sd-jwt-vc (+1/-1/💬3)
1 issues created:
- 8.1.2. Rendering Method "svg_template" differs from Example B.2 (by
queekusme)
https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/374
2 issues received 3 new comments:
- #374 8.1.2. Rendering Method "svg_template" differs from Example B.2 (2 by
bc-pi, queekusme)
https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/374
- #355 A new field called "Issuer Authorization URI - "iss_auth"" (1 by bc-pi)
https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/355 [pending close] [future-extension] [policy]
1 issues closed:
- A new field called "Issuer Authorization URI - "iss_auth"" https://github.com/oauth-wg/oauth-sd-jwt-vc/issues/355 [pending close] [future-extension] [policy]
* oauth-wg/draft-ietf-oauth-attestation-based-client-auth (+0/-0/💬9)
4 issues received 9 new comments:
- #153 Should this document be applicable both to Authorization Servers and
Resource Servers ? (1 by paulbastian)
https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth/issues/153 [ready-for-pr]
- #152 Attestation-based authenticated Client. Public or Confidential? (6 by VinodAnandan, babisRoutis, jogu, paulbastian, tplooker)
https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth/issues/152 [discuss]
- #151 Ambiguity concerning MAC algorithms in Client Attestation JWT (1 by paulbastian)
https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth/issues/151 [ready-for-pr]
- #139 Clarify IANA Registration for headers (1 by tplooker)
https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth/issues/139 [pending-close]
* oauth-wg/oauth-identity-assertion-authz-grant (+1/-1/💬3)
1 issues created:
- Security recommendations for IdPs (by sdesen)
https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/issues/61
2 issues received 3 new comments:
- #61 Security recommendations for IdPs (1 by sdesen)
https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/issues/61
- #52 Discovering allowed Resource App (instances) for the logged in user (2 by mcguinness, sdesen)
https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/issues/52
1 issues closed:
- Clarify subject identifier in ID-JAG https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/issues/59
* oauth-wg/draft-ietf-oauth-client-id-metadata-document (+0/-0/💬1)
1 issues received 1 new comments:
- #41 Feedback: Developer Experience Improvement (1 by ThisIsMissEm)
https://github.com/oauth-wg/draft-ietf-oauth-client-id-metadata-document/issues/41
Pull requests
-------------
* oauth-wg/oauth-browser-based-apps (+1/-0/💬0)
1 pull requests submitted:
- (by teraa)
* oauth-wg/oauth-transaction-tokens (+1/-0/💬0)
1 pull requests submitted:
- (by tulshi)
* oauth-wg/oauth-sd-jwt-vc (+1/-0/💬0)
1 pull requests submitted:
- (by queekusme)
* oauth-wg/oauth-identity-assertion-authz-grant (+2/-0/💬2)
2 pull requests submitted:
- (by sdesen)
- (by sdesen)
2 pull requests received 2 new comments:
- #62 Change refresh token langugae that implies id-jags should be long lives
(1 by mcguinness)
https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/pull/62
- #60 ID-JAG Claim Description Updates (1 by aaronpk)
https://github.com/oauth-wg/oauth-identity-assertion-authz-grant/pull/60
Repositories tracked by this digest:
-----------------------------------
* https://github.com/oauth-wg/oauth-browser-based-apps
* https://github.com/oauth-wg/oauth-identity-chaining
* https://github.com/oauth-wg/oauth-transaction-tokens
* https://github.com/oauth-wg/oauth-sd-jwt-vc
* https://github.com/oauth-wg/draft-ietf-oauth-resource-metadata
* https://github.com/oauth-wg/oauth-cross-device-security
* https://github.com/oauth-wg/oauth-selective-disclosure-jwt
* https://github.com/oauth-wg/oauth-v2-1
* https://github.com/oauth-wg/draft-ietf-oauth-status-list
* https://github.com/oauth-wg/draft-ietf-oauth-attestation-based-client-auth
* https://github.com/oauth-wg/oauth-identity-assertion-authz-grant
* https://github.com/oauth-wg/draft-ietf-oauth-rfc8725bis
* https://github.com/oauth-wg/draft-ietf-oauth-rfc7523bis
* https://github.com/oauth-wg/oauth-first-party-apps
* https://github.com/oauth-wg/draft-ietf-oauth-client-id-metadata-document
--
To have a summary like this sent to your list, see:
https://github.com/ietf-github-services/activity-summary
_______________________________________________
OAuth mailing list -- [email protected]
To unsubscribe send an email to [email protected]
