Page 1 of 2 12 LastLast
Results 1 to 5 of 7

Thread: verifying windows credentials via C DLL

Hybrid View

  1. #1
    Join Date
    Aug 2007
    Posts
    22

    verifying windows credentials via C DLL

    Hi folks,

    In a previous installer, we have code that calls a Windows DLL to verify user credentials. The LibraryLoader class is utilized to do so.

    I can't seem to find an equivalent method for doing this.

    Generically I see this as calling a Windows DLL from a custom action.

    What would be a solution to this problem, either specifically or generically?

    Thanks!

    - john

  2. #2
    Join Date
    Mar 2006
    Location
    Paris, France
    Posts
    2,037

    Exclamation

    There used to be an IsUserAdmin plugin, but it's been a while since it has been discontinued and thus removed from the list of downloadable files & utilities. I'm afraid I don't understand though why exactly the previous method you used no longer works. Nevertheless, there is a method in the IA API that allows you to check if the user that has launched the installer is Windows admin or not (it's in an API that has been inherited from InstallShield, actually).
    Vlad

  3. #3
    Join Date
    Aug 2007
    Posts
    22
    The problem is not if the current user is an admin or not. The problem to solve is validating that any user-supplied account name and password exists and is valid.

    In my scenario, the user can choose if a service to be installed is run as LocalSystem or as a named account. We would like to verify that the specified user exists and the password is valid before registering the service with that information.

  4. #4
    Join Date
    Mar 2006
    Location
    Paris, France
    Posts
    2,037

    Exclamation

    AFAIK, there is no builtin support for that, so you would need custom code, unless there are platform specific functions to do that.
    Vlad

  5. #5
    Join Date
    Aug 2007
    Posts
    22
    My only issue at the moment is making a Windows DLL be available during the pre-install phase.

    I've seen workarounds of:
    1) creating a seperate install for it and run it prior to the pre-install step (yuck!)
    2) modifying the JVM zip file to include the file (ewwww)

    Any better solutions?

    Thanks!

    - john

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •