A form allowing password login plus "forgot password" facility

RaptorRaptur

New member
Local time
Today, 18:29
Joined
May 15, 2021
Messages
24
Hi All,

I need to create a login/control system that will control:

1. All users to access certain menus/modules
2. Several other levels to access more sensitive menus/modules
3. It should have a reasonably secure facility for new users to create their own logins/passwords etc (In much the same way as most forums do)
4. Likewise a facility for handling forgotten user names/passwords (In much the same way as most forums do)
5. Regarding 3 and 4 some form of confirmation via eMail and/or Cell phone PLUS confirmation from the SysAdmin.

I am currently using a ListBox based Menu system that will easily allow me to set levels on every menu/module, soi i think that will solve most of the complexity related to 1 and 2 above.

I am still in the planning stage (paper and pencil :) ) but would really appreciate any tips and tricks from anyone. (Why reinvent the wheel?)

Regards

Alan
 
If your systems are on Active Directory, you can get logged user ID from AD and forgo all the password stuff.
 
My systems will be running on small LAN driven networks. In some cases even on single stand alone PCs.
I can't rely on any external security facilities as I will have little, if any, control over the environments.
I don't know anything about Active Directory, What is it?
 
My systems will be running on small LAN driven networks. In some cases even on single stand alone PCs.
I can't rely on any external security facilities as I will have little, if any, control over the environments.
I don't know anything about Active Directory, What is it?
Active directory is part of a Windows server setup. It provides authentication and security for all computers connected to it.
I don't see how you can provide security on independent computers running simple file sharing or standalone. To do password reset, you will need some type of administrator account.
 
Active directory is part of a Windows server setup. It provides authentication and security for all computers connected to it.
I don't see how you can provide security on independent computers running simple file sharing or standalone. To do password reset, you will need some type of administrator account.
In most cases, i will have little, if any, control over their networking. In some cases we might have a SQLServer back end but the majority will be running on a split Access system with Jet as the database.
Respectfully, I think I disagree about the need for the administrator account. Surely the automated system used by almost all web sites that demand UserNames and Passwords could be effective.
Before anyone jumps on me, I am fully aware that Access alone does not provide,in any way, a bullet proof security/password facility. I have factored that in to my design decisions.
Thank you, I really do appreciate your input
 
In most cases, i will have little, if any, control over their networking. In some cases we might have a SQLServer back end but the majority will be running on a split Access system with Jet as the database.
Respectfully, I think I disagree about the need for the administrator account. Surely the automated system used by almost all web sites that demand UserNames and Passwords could be effective.
Before anyone jumps on me, I am fully aware that Access alone does not provide,in any way, a bullet proof security/password facility. I have factored that in to my design decisions.
Thank you, I really do appreciate your input
If you want to always be able to recover your customer's DB, you will need some sort of back door. You can have Access send an email with a on-time unlock code, but what if it can't connect to you email server? What if your user changes the email system and address?
 
So long as you are using ACCESS on a windows machine, you should be able to get the current UserName for the user logged in to the machine.

This would allow you to have the OS handle login / password without you needing to do much special. Then your end users IT can be in charge of making sure their username and password are updated while you just grab who has logged in.
 
So long as you are using ACCESS on a windows machine, you should be able to get the current UserName for the user logged in to the machine.

This would allow you to have the OS handle login / password without you needing to do much special. Then your end users IT can be in charge of making sure their username and password are updated while you just grab who has logged in.

True, Mark_, but there is the small matter that if this is a stand-alone single machine, the person COULD have just put a password on the OWNER account (which all Windows PCs have when the O/S is first loaded).

In most cases, i will have little, if any, control over their networking. In some cases we might have a SQLServer back end but the majority will be running on a split Access system with Jet as the database.

This comment leads to confusion as to the scope of the required solution. Just how many different applications or different instances of application are we talking about? Having an SQL Server back-end and also having a split Access JET backend is kind of unlikely if this is a single system. So what exactly ARE we discussing?
 
Hi All,
The majority of my systems (FE and BE using Jet) are running on single machines or on small networks (4 to 8 workstations. Nevertheless, even on the single machine I have to allow for more than one user and/or the fact that the owner may not want certain info to be available to any of the other users.
My issue is that I am now designing a new application and want to have on e set of code that can work across the range of Single machine (Jet) through MySQL and SQL Server. I therefore need a reasonably robust login/password system for the lower end. The people who are wanting/needing a SQL backend would be able to add on additional security. I am using a system of ListBox driven menus that allow me to turn on/off aspects of the programme not needed at any specific site with no coding necessary
 
My first thought on this topic was comparing web features and Access capabilities could be misleading, since they’re two different architectures. Taking a web feature and using it as an inspiration for creating an Access function is good, but I wouldn’t go as far as saying if the web can do it, then Access should also be able to as well.

I am a little concerned about allowing the user to reset their password without any admin intervention. If not done correctly, it could allow anyone to impersonate other users and reset their password and therefore allow them to get unauthorized access to sensitive data.

As for email confirmation, my other concern is if your application could be installed on systems that use the modern Outlook. You’ll have to perhaps account for that.

Just my 2 cents…
 
here is a simple db that employs Login form.

username/password: common => will have limited access on the db.
username/password: arnel/nozup => admin account, have unlimited access and can set/assign user and user-right to the system.
 

Attachments

Users who are viewing this thread

Back
Top Bottom