Add expiration date to consent sessions.

ory / hydra

OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid.

Apache License 2.0

15.45k stars 1.48k forks source link

Preflight checklist

[X] I could not find a solution in the existing issues, docs, nor discussions.
[X] I agree to follow this project's Code of Conduct.
[X] I have read and am following this repository's Contribution Guidelines.
[ ] This issue affects my Ory Network project.
[X] I have joined the Ory Community Slack.
[x] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

Currently it is not possible to expire a consent session (revoke refresh and access token). While the refresh token remains active, it can only be revoked through manual intervention. In compliance with the PSD2 regulation, Payment Service Users (PSUs) must provide their consent again every 180 days. If a PSU does not renew their connection, the connection must be terminated. ASPSP (banks) could leverage Hydra to expire the consent session and eventually let users (PSU) renew their consent from the bank's application dashboard.

Describe your ideal solution

A new field expire_at in the hydra_oauth_flow table exists. The field should contain the consent session expiration date
An admin endpoint to extend the expiration date must exist.
A janitor command to revoke expired consent sessions must exist
"List OAuth 2.0 Consent Sessions of a Subject" must contain the expiration date.

Workarounds or alternatives

Having separate database storage in a separate service which includes the expiration date and keep it in sync with Hydra.

Version

v2.1.2

Additional Context

No response

Hello contributors!

I am marking this issue as stale as it has not received any engagement from the community or maintainers for a year. That does not imply that the issue has no merit! If you feel strongly about this issue

open a PR referencing and resolving the issue;
leave a comment on it and discuss ideas on how you could contribute towards resolving it;
leave a comment and describe in detail why this issue is critical for your use case;
open a new issue with updated details and a plan for resolving the issue.

Throughout its lifetime, Ory has received over 10.000 issues and PRs. To sustain that growth, we need to prioritize and focus on issues that are important to the community. A good indication of importance, and thus priority, is activity on a topic.

Unfortunately, burnout has become a topic of concern amongst open-source projects.

It can lead to severe personal and health issues as well as opening catastrophic attack vectors.

The motivation for this automation is to help prioritize issues in the backlog and not ignore, reject, or belittle anyone.

If this issue was marked as stale erroneously you can exempt it by adding the backlog label, assigning someone, or setting a milestone for it.

Thank you for your understanding and to anyone who participated in the conversation! And as written above, please do participate in the conversation if this topic is important to you!

Thank you 🙏✌️

ory / hydra