|
|
 |
|
|
|
User credential management – system level vs. application level
microsoft.public.windowsxp.embedded
|
|

04-02-2008, 04:36 PM
|
|
|
|
User credential management – system level vs. application level
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
|
|

04-02-2008, 05:34 PM
|
|
|
|
Re: User credential management - system level vs. application level
On Apr 2, 12:36*pm, Tony Brown <Tony Br...@discussions.microsoft.com>
wrote:
> 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 ourown
> 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
I'm not entirely sure how your application uses different rights, but
perhaps the CreateProcessWithLogonW function from advapi32.dll would
help. It is the programmatic equivalent of "Run As" in Explorer. We
use that in our systems for certain things. You just need to make sure
that you add the "RunAs Service" component to your image to use it.
|
|

04-02-2008, 09:35 PM
|
|
|
|
Re: User credential management – system level vs. application level
Tony,
Just wondering why do you have to switch Windows users if your app has its
own set of user credentials?
--
=========
Regards,
KM
> 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
|
|

04-03-2008, 02:31 PM
|
|
|
|
Re: User credential management – system level vs. application level
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@discussions.microsoft.com> wrote in message
news:17C0A33F-8F91-4671-A038-4D71498EF663@microsoft.com...
> 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
>
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT. The time now is 10:22 AM.
|
|