I agree with Dick’s observation about the privacy implications of using an Introspection Endpoint. That’s why it’s preferable to not use one at all and instead directly have the Resource understand the Access
Token. One way of doing this is the JWT Access Token spec. There are plenty of others. The downsides of using an Introspection Endpoint should be described in the Privacy Considerations section. -- Mike From: OAuth <oauth-bounces@xxxxxxxx> On Behalf Of
Dick Hardt On Wed, Aug 26, 2020 at 4:37 AM Torsten Lodderstedt <torsten=40lodderstedt.net@xxxxxxxxxxxxxx> wrote:
As I see it, the privacy implication is that the AS knows
when the client (and potentially the user) is accessing the RS, which is also an indication of
when the user is using the client. I think including this implication would be important to have in a Privacy Considerations section. /Dick ᐧ |
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call