-
Notifications
You must be signed in to change notification settings - Fork 166
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
Like putting the login page at the beginning so that the user only has access after logging in. #261
Comments
Hello, there are some examples on closed issues , look at #78 . I personally did it more simple, just put the logic in index.php checking if valid user is logged, if not redirect to login.php . I use LDAP in my environment, then after validation redirect to the requested page. |
Hi, thanks for the help. |
Look here https://github.com/Esysc/SPOT/blob/master/provisioning/login.php It's a very basic example. You have the login form and validation then all pass through the session . The index.php check a valid session before to redirect. You have in the same direct ory the original login that refers to a dB users table.
|
Hi, |
Hello, you can use the example if you prefer and look orders threads. I simply check a session variable, not so elegant, but the app runs on corporate. Look in index.php, if the session is not set redirect to login.php . This script validate the user then redirect to the requested url. I put the check in index.php because every routed url pass there. |
Hello |
Don't know if I have understood., but the code is just an example, cannot run in your environment. I proposed you just to give a look for inspiration. Bit not copy and paste as is |
Ok, I got confused I thought this project you were doing was using phreeze frameworks, because it's a good framework for beginners, but the bad part is we do not have much information about it. |
Hi, I'd like to know how to put the login page in the beginning so that the user only has access to log on first.
Thank you very much in advance!
The text was updated successfully, but these errors were encountered: