How would i run my application as a admin insted of rightlicking and choose rus as?

[Arjay]

I need to have the the admin credentials stored inside my application

Do you think that this is a good idea? What happens if the account or domain changes? Would that break your application?

[BigEd781]

Do you think that this is a good idea? What happens if the account or domain changes? Would that break your application?

I asked the same thing, but got the reply

no they wont have a clue what creds are in the application i just want to authenticated the application to it runs as a admin instead of having to right lick and run it as a admin then entering creds .... i will be changing the password for that account with in my app using updates for the program...

So who knows.

[summey]

the account wont change it will be static administer account i set up in AD and monitor it for use other then being stored inside my code to run this app i just dont know how to do that.... . No way it can be changed unless someone decompiles my app changes it and recompiles it... highly unlikely ... all this does iis unlock locked out users right now i have list the locked out users in a combo box... also im going to set up updates when i build this app so it checks for updates so once a month i can change the password re build and when my app is executed it will look for updates and changes the password the user using it hasnt a clue whats going on except he is unlocking accounts.
it works great i just want a normal users account to be able to run this one app as a admin so it can unlock that locked out users.

Thank you for your time.

[Arjay]

Storing logon hardcoded account information inside the app is a security issue - it's not about changing the hardcoded information and recompiling the app, it's about gaining access to the information.

You may consider hosting a service for this functionality. The service can run under any account information and you can limit access to the service through AD. Then the client app simply connects to the service and wouldn't need any elevated permissions.

[summey]

Storing logon hardcoded account information inside the app is a security issue - it's not about changing the hardcoded information and recompiling the app, it's about gaining access to the information.

You may consider hosting a service for this functionality. The service can run under any account information and you can limit access to the service through AD. Then the client app simply connects to the service and wouldn't need any elevated permissions.

Where would be a good place to read up on how to do something like that?

Thank you for your time
-Summey