-
Notifications
You must be signed in to change notification settings - Fork 1k
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
dbAuth.returnedColumns also affects $_SESSION['user'] #1052
Comments
Did the authorization middleware help you? Or was that limiting? Or you want to prevent it from ending up in the session variable? Is that it? I suggest creating a view in that case. |
The authorization middleware is limiting. Basically, I have columns in my user table for user/password for another API script (also php) I'm not sure how a view would be helpful in this specific case. Please let me know if it is still unclear. |
Are you sure that that is what you want? Isn't that insecure?
It seems the code does this, so it is intended not to have the password in there.
Why? Because of performance? |
I'm in full control of the backend, so not really I think.
It is not the user's password used for authentication. It is a password for another API, which my backend is used as a proxy to connect to.
Performance is a consideration, but mostly convenience. |
Then it return the session variable's contents:
So I guess the answer is: No, there is (currently) no way to do it. |
Hi,
I'd like to store some user metadata in the user session to use it in another api endpoint, but not return it to the frontend.
Is there a way to do it?
The text was updated successfully, but these errors were encountered: