[jbosstools-issues] [JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User

Thomas Mäder (JIRA) issues at jboss.org
Tue Apr 19 16:04:00 EDT 2016


    [ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194048#comment-13194048 ] 

Thomas Mäder commented on JBDS-3841:
------------------------------------

I'm sure we could come up with a way to pass the original user to the post-UAC part. However, if we require admin privileges, why do we install for a single user? Normally, when you install a program, you either put it in the users home directory (no admin required) or you install it for everybody. 
Why do we even need admin priviliges if we only try to update the user's environment? That should be possible without admin access.
If we need an admin account to run the installer, we should not use UAC, but simply refuse to start from a non-admin account.

> Installer Sets Path for Wrong User
> ----------------------------------
>
>                 Key: JBDS-3841
>                 URL: https://issues.jboss.org/browse/JBDS-3841
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: installer
>    Affects Versions: 9.x
>         Environment: Windows 10
>            Reporter: Thomas Mäder
>            Assignee: Denis Golovin
>            Priority: Blocker
>             Fix For: 10.0.0.Alpha1
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)



More information about the jbosstools-issues mailing list