[AccessD] Using Windows Authentication with Access/SQL Apps

Not necessarily.  Our company/IT department has just implemented a SSO (single sign on) application company wide.  I agree with you that leaving a machine unattended gives access to every app on my machine...I'll even go a step further and say it is down right silly when my Outlook closes due to inactivity...and the SSO instantly signs it back in.
 
As for the question.  I have not done it with SQL Server...but in Access FE/BE situation...I have turned off the shift-by-pass...and on open the FE checks who is logged on the machine...and validates that username against a table.  The table actually already existed...the user IDs mimicked their Windows ID...and I used it to lookup/display the users full names on reports.  So I didn't even have to change the model.  
 
If the user is not in the table...the app closes.  This has come in handy...as users can no longer share IDs and passwords for the app and they don't have a password to remember other than Windows.
 
Good Luck,
 
Mark A. Matte
 
 
 
 
 
 
 
 
 
 

> Date: Tue, 25 Nov 2008 14:11:40 -0800
> From: cfoust at infostatsystems.com
> To: accessd at databaseadvisors.com
> Subject: Re: [AccessD] Using Windows Authentication with Access/SQL Apps
> 
> If your client has an IT department, they are currently screaming bloody
> murder over that idea. It means you're leaving your SQL Server database
> at the mercy of any user who logs onto windows and then goes for a long
> coffee break leaving someone else to poke around in their machine.
> 
> Charlotte Foust 
> 
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
> Sent: Tuesday, November 25, 2008 9:58 AM
> To: 'Access Developers discussion and problem solving'
> Subject: [AccessD] Using Windows Authentication with Access/SQL Apps
> 
> I'm working on upsizing one of my customers to SQL. They have asked if
> we could eliminate the Access workgroup username and password login that
> I currently use (mostly just so the database knows who is logging in).
> 
> With SQL using Windows Authentication, my Access app could simply pick
> up on the current username and go from there, without going through an
> additional username and password entry.
> 
> Has anyone done this? Any pros, cons, or gotchas?
> 
> Thanks!
> Dan
> 
_________________________________________________________________
Color coding for safety: Windows Live Hotmail alerts you to suspicious email.
http://windowslive.com/Explore/Hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_safety_112008