Repository navigation
Session id handler #202
Description
Activity
You mean this one, right? https://forum.nette.org/en/34621-do-not-save-sessions-on-authorization-in-api-access
Imho all you need is to implement
Nette\Security\UserStoragewhich would use simple array instead of session and set it as storage to user, nothing more. Maybe also createApiUser extends Nette\Security\Userand register it as a separate service so it's easier to work with.Nope, it won't work. In most cases we have session data (yes I know api should be stateless but doesn't really work in my case) only if I can set session_id on my own I'll be able to solve this without a lot of refactoring.
I don't understand this issue. Session ID can be set with
session_id(...), isn't it?
In some cases (api for example) we need to be able not to use cookies for reading/writing session id but rather handle session_id reading writing on our own... I already saw a few forum posts regarding that and I am also in simmiliar situation now that having such a feature is kinda a must. I could also prepare PR, but want to hear a few thoughts first....