From github at oidf.org Tue Jun 2 17:03:27 2026 From: github at oidf.org (github at oidf.org) Date: Tue, 2 Jun 2026 17:03:27 +0000 Subject: [Openid-specs-risc] openid/sharedsignals: Comment created on issue 334 Message-ID: openid/sharedsignals event Issue Comment created on issue 334 Issue Title: Closes #332 - Fix scopes section https://github.com/openid/sharedsignals/pull/334 Comment: > @appsdesh thanks for the comment. can you take a look at the updated wording and let me know what you think? LGTM! thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From github at oidf.org Tue Jun 2 17:25:02 2026 From: github at oidf.org (github at oidf.org) Date: Tue, 2 Jun 2026 17:25:02 +0000 Subject: [Openid-specs-risc] openid/sharedsignals: Issue 332 closed Message-ID: openid/sharedsignals event Issue 332 closed Issue Title: scope section wording is odd https://github.com/openid/sharedsignals/issues/332 -------------- next part -------------- An HTML attachment was scrubbed... URL: From github at oidf.org Tue Jun 2 17:58:55 2026 From: github at oidf.org (github at oidf.org) Date: Tue, 2 Jun 2026 17:58:55 +0000 Subject: [Openid-specs-risc] openid/sharedsignals: Comment created on issue 327 Message-ID: openid/sharedsignals event Issue Comment created on issue 327 Issue Title: Clarify how a Receiver discovers the Authorization Server from a Transmitter URL https://github.com/openid/sharedsignals/issues/327 Comment: I'd suggest: The Authorization Server MAY distribute discovery metadata (such as the authorization endpoint) via Authorization Server Metadata as specified in RFC8414. How the receiver determines the Authorization Server to be used is out of scope. -------------- next part -------------- An HTML attachment was scrubbed... URL: