🤗 [Question]: How to retrieve all session data from middleware sessions？

[Flashcqxg]

Question Description

How to retrieve all session data from middleware sessions (Fiber v2 and Fiber v3)? If possible, could a GetAll method be added to return all data in the session?
(from the memory storage)

Code Snippet (optional)

Checklist:

• I agree to follow Fiber's Code of Conduct.
• I have checked for existing issues that describe my questions prior to opening this one.
• I understand that improperly formatted questions may be closed without explanation.

[ReneWerner87]

in v3 we have the new method
Keys()

@sixcolors can you support here

[sixcolors]

@ReneWerner87 is right — the correct way to retrieve all session data is using Keys() and then Get().

Since session data is stored internally as a map (data), we could technically return a copy of the whole map in a GetAll() method. But you’d still need to loop over it or extract keys, so I don’t see much API benefit.

I also rarely see a real use for GetAll() or even Keys(), since you usually know the keys you’ve set and access session data explicitly.

If there’s a use case where looping over keys or explicit gets isn’t enough, I’m open to hearing it — maybe I’m missing something.

[Flashcqxg]

Sorry, perhaps I didn’t explain my needs clearly. Here’s what I’m trying to achieve:

I store all users' session data in memory, including userid, username, ip, and other information.

Suppose 20 different users have logged into the system—I now want to display all 20 users' userid, username, and ip on the frontend.

The current func (m *Middleware) Keys() []any only retrieves the userid, username, and ip of the current session.
But what I need is to fetch all users' userid, username, and ip information.

[sixcolors]

Thanks for clarifying. What you're asking for isn’t about retrieving all keys in a single session — it’s about accessing all sessions across all users.

Fiber doesn't track session IDs internally, and the Store interface doesn’t expose a way to list all sessions. This is by design — not all supported backends allow safe or efficient enumeration.

That said, in Fiber v3, you can use store.GetByID(sessionID) to fetch any session. If you track session IDs yourself (e.g., on login), you can retrieve userid, username, ip, etc. for all users that way.

Alternatively, you could implement your own custom storage backend (e.g., based on memory, Postgres etc), and add methods like ListSessions() at the store level. But be aware that session.Get() works on a copy of the session data loaded when the session is initialized, so direct changes to the store won’t reflect unless reloaded. Similarly session.Save() will overwrite any changes made since data was retrieved.

Also, once you step outside the default session handling model, locking and concurrency become your responsibility. You’ll need to fully understand how your code interacts with the session store and handler, especially in concurrent request environments.