Hello everyone! I hope that you all are well going . Actually from past few months , I am working on a website name “Bhuvan Aerospace” . Though the results are satisfactory, but still i am worried, as the login page shows the usernames along with the passwords…Bhuvan Aerospace limited
if you want suggestions you will want to share your repository with your codebase, not your live link. With the live link you are only going to get UI/UX feedback
2 Likes
The project looks interesting, especially the progress you’ve made over the past few months. One important thing to address is the login system displaying usernames and passwords. Passwords should never be stored or displayed in plain text. I’d recommend using proper password hashing and secure authentication practices before deploying the site publicly. It would also be worth reviewing how user credentials are stored and handled on the backend. Good luck with the project!
1 Like
well sir, you are right…At first i thought to do that, but when i tried to paste my source code here, it is showing “Exceeded word limit !”… So, please provide me a solution for it…
Thank you sir for such a valuable suggestion…well, along with this, can you please describe these ways or methods in a more detailed manner, so that i can secure the user credinals (specifically, i want to know whether there are any websites or apps by using which i can do this work for free)?
are you not using github or something like that?
no sir, and thats the issue…moreover, this whole website is made without a server, i.e, this website dosen’t has a server…
if you want to implement login you must have a server
please work through the back end curriculum https://www.freecodecamp.org/learn/back-end-development-and-apis-v9/
1 Like
Hello! If the login page is displaying usernames together with passwords, I would treat that as a serious security issue, even if the website is still under development.
First, check whether the passwords are actually being stored or displayed in plain text. Passwords should never be exposed on the login page or stored as plain text. They should be securely hashed, and the login form should only display masked password input.
I’d also recommend checking the browser’s developer tools and network requests to make sure credentials aren’t being sent or returned unnecessarily. If this is a Netlify-hosted project, review how authentication and environment variables are configured as well.
Before making the site public, I’d fix the authentication flow and test it thoroughly. It’s much better to address this now than after real users start creating accounts.
Thank you sir for your valuable suggestion, but can you please guide me how to securely hash them?
Thank you sir for your valuable help
Hello everyone ! After sir has provided me with a valuable link, I am able to learn the backend engineering very well…but still I am getting troubles. It is so because whenever I install the node.js in my system and try to attach it directly to my website, it creates either a glitch or an error… So anyone can provide be a guidelines regarding how to implement it on my website?
please don’t call me “sir”
1 Like
Well, that’s a good idea, but I were you, i would like to start from something which is more easy to manage and basic in nature…
I can understand that it is very annoying, and i apologise for it… Actually, the fact is that I use to respect my elders ( those whom I meet first time )with this salutation…
Hi! The website looks like it has come a long way, but displaying usernames together with passwords on a login page is a serious security concern. Passwords should never be stored or displayed in plain text.
I’d recommend reviewing the authentication system and ensuring that passwords are securely hashed on the server side, rather than being exposed in the frontend or database. Also check whether the login page is using HTTPS, whether sensitive credentials are accidentally included in the page source or JavaScript, and whether proper authentication and session management are implemented.
If these are only demo credentials for testing, it would still be better to clearly label them as test accounts and avoid using real passwords. Before making the site public, I’d definitely address this issue and run a basic security audit.
1 Like
I agree with this point here. GitHub would make this much easier. You could push the project there and share the repository.
I absolutely agree with you all, but the thing is that how to use GitHub and hashtags for this purpose, i don’t know…so, can anybody provide me this problem 's solution to me?
I am not sure I understand what you are asking? you can upload your code to github to share it with people
what do you mean by “hashtag” in this case?
do you mean hashing? if so please start the back end certificate and work through it, it will answer many questions about authentication
Yes, sir you got it right! And thanks for the suggestion…