ory / network

Ory runs a global end-to-end security infrastructure for humans, robots, and servers. We build and use open source software.
Apache License 2.0
80 stars 6 forks source link

include current session on /sessions #156

Open till opened 2 years ago

till commented 2 years ago

Preflight checklist

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 commented 2 years ago

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

vsumit89 commented 2 years ago

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 commented 2 years ago

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] commented 1 year ago

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

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 commented 1 year ago

@aeneasr Still being done?

github-actions[bot] commented 1 day ago

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

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