-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bookworm + portal rework #342
Conversation
…of classic JSON for credentials ...
Allowing login from simple HTML form Also allow to pass username/password as two params instead of a combined "credentials"
Moulinette logging is an unecessarily complex mess, episode 57682
Tweaks and fixes for new portal API / ssowat refactoring
…cified, I guess that's okay
I don't think a6c7e55 fixes YunoHost/issues#2238 The cookie should be deleted by the client but other copies of it (or if the client doesn't honor the request) remain valid for SSOWat... or did i miss something? So that's more like "delete cookies" than "logout" effectively, which i think is a security problem. EDIT: This should have been fixed in the meantime |
…APIs are hell to debug ~_~
…nually launching yunohost APIs to debug them
…ings significantly for stuff that calls a lot of hooks...
portal-api: Bypass CSRF protection for login route
portal-api: login/logout redirect to referer when param referer_redirect is set
I think all the building blocks are here to have a portal without javascript. I'll try and let you know. Thanks a lot!!! |
Soooo after messing around a little bit i realized we don't have the building blocks at all: yunohost-portal-api has no privileged API for a backend/daemon to know what permissions a user has, which was possible previously with |
No description provided.