Re: User credential management – system level vs. application level
- From: "Sean Liming \(MVP\)" <sean_liming@xxxxxxxxxxxx>
- Date: Thu, 3 Apr 2008 23:31:30 +0900
Why not one account with a single password? You could create a back door password for an administrator to access things like control panel.
Regards,
Sean Liming
www.sjjmicro.com / www.seanliming.com
Book Author - XP Embedded Advanced, XP Embedded Supplemental Toolkit
"Tony Brown" <Tony Brown@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:17C0A33F-8F91-4671-A038-4D71498EF663@xxxxxxxxxxxxxxxx
Hello,
We are currently using AutoAdminLogon in the registry to get logon to
windows XP embedded, we then launch our application with an entry in the Run
key. We manage security to various features of our application with our own
set of user credentials.
Some users need to have system administration privileges, and other users
should not.
I am looking for advice related to two issues we are having with this
implementation.
1. Switching Windows OS users is slow and causes our application to close
2. We end up with two sets of username/password credentials, one for the OS
and one for our application.
Ideally, we would like to manage logon credentials in one location, allow
quick user switching, and have the same UI application for each user.
All advice is appreciated,
Thank you,
Tony Brown
.
- References:
- User credential management – system level vs. application level
- From: Tony Brown
- User credential management – system level vs. application level
- Prev by Date: Re: Encrypt compact flash (system partition) or Secure compact flash
- Next by Date: Re: Group Policy Configurations
- Previous by thread: Re: User credential management – system level vs. application level
- Next by thread: FBWF problem with removeable drive in system
- Index(es):
Relevant Pages
|
