include current session on /sessions

[till]

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.
• [X] This issue affects my Ory Cloud project.
• [X] I have joined the Ory Community Slack.
• [X] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

I would like the current session to be included in /sessions to avoid multiple calls to list all sessions.

Follow-up to: #134

Describe your ideal solution

GET /sessions returns all sessions of the current user.

Workarounds or alternatives

Combine calls from GET /sessions and GET /sessions/whoami

Version

cloud

Additional Context

No response

[aeneasr]

Yes, we definitely need to do this. Maybe add a flag indicating the current session?

[vsumit89]

Is this issue fixed? Any timeline by which this fix will be released. If I were to contribute to fixing the issue, can you direct me on how to go about it?

[till]

Yes, we definitely need to do this. Maybe add a flag indicating the current session?

I liked the previous API where it was included, but you couldn't delete it. IMO plenty to reduce the set in the client.

[github-actions[bot]]

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 🙏✌️

[till]

@aeneasr Still being done?