How to make use of SSO in Ms Access?

[prabha_friend]

Yes. You are right. "Single Sign On"

 

[561414]

With a launcher form where users login.

Include a token with expiration date while processing the credentials. Store the token somewhere, a file, regkey, etc. When using any form in any access app that requires this authentication, validate the token on open.

And so on

 

[prabha_friend]

Sorry for not asking clearly... Utilising the office SSO. For example, if an employee access my system it has to validate his already existing office credentials. I don't want them to have a separate credentials for my access database. Possible?

 

[NauticalGent]

Here is a VB Script to extract a users' credentials from the Active Directory (AD).

You can adapt it to VBA almost as it is written. I use it to compare against a my user table (tblUsers) and if there are found, show the main menu, if not the app quits.

 

[prabha_friend]

Here is a VB Script to extract a users' credentials from the Active Directory (AD).

You can adapt it to VBA almost as it is written. I use it to compare against a my user table (tblUsers) and if there are found, show the main menu, if not the app quits.

What is the difference between "Environ" and AD

 

[NauticalGent]

What is the difference between "Environ" and AD

I am not really sure. Others on this Forum (@sonic8 and @isladogs) have mentioned that the Environ() functions can be hacked so this may be a more secure way to getting the credentials that you want.

 

[The_Doc_Man]

"Environ" comes from pre-defined named symbols currently created by the Windows Login process. They are a hold-over from the days of MS-DOS, which used them as a way to identify things like a device or path search string (a list of folders to search for programs). However, those environment symbols are not always protected from user modification. That, too, is a hold-over from DOS. A user in a less controlled domain could "spoof" a "username" or "computername" symbol. Getting the info from Active Directory calls is more stringent because AD login information is read-only even in a loosely managed domain.

 

[NauticalGent]

"Environ" comes from pre-defined named symbols currently created by the Windows Login process. They are a hold-over from the days of MS-DOS, which used them as a way to identify things like a device or path search string (a list of folders to search for programs). However, those environment symbols are not always protected from user modification. That, too, is a hold-over from DOS. A user in a less controlled domain could "spoof" a "username" or "computername" symbol. Getting the info from Active Directory calls is more stringent because AD login information is read-only even in a loosely managed domain.

That is what I was going to say, but I cant type as fast as you...