[jbosstools-issues] [JBoss JIRA] (JBDS-3052) Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBDS-3052:
-----------------------------

    Release Notes Text: 
Should document the fact that to enforce a multi-user install on Windows, the shared install folder must correctly be configured to be READ ONLY for all standard users.

See also: http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fmisc%2Fmulti_user_installs.html 

  was:Should document the fact that to enforce a multi-user install on Windows, the shared install folder must correctly be configured to be READ ONLY for all standard users.



> Shared install on Windows will only use private folders for updates/workspace if the shared install folder is read only
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-3052
>                 URL: https://issues.jboss.org/browse/JBDS-3052
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Story
>      Security Level: Public(Everyone can see) 
>          Components: installer
>    Affects Versions: 8.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 8.0.0.Beta2
>
>         Attachments: jbds8b2-windows8.1-child-user-private-install-updated-via-central.png, jbds8b2-windows8.1-shared-install-readonly-now-installs-into-users-kid-.eclipse-folder.png, jbds8b2-windows8.1-standard-user-install-error-in-central.png, jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png, jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png, jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png, w-shared-install-jbdevstudio-security-permissions-remove-authenticated-users.png, w-shared-install-jbdevstudio-security-permissions.png, win81pro-details.png
>
>
> To test the user experience on Windows, I created three accounts:
> * nboldt (my own admin user)
> * {color:orange}*dummy*{color} (a standard user)
> * {color:green}*kid*{color} (a child user, which is a standard user but with Family Safety logging - http://windows.microsoft.com/en-ca/windows-8/create-child-account )
> Both the child and standard users were able to install JBDS into their own home folders and perform an installation from Central:
> !jbds8b2-windows8.1-child-user-private-install-updated-via-central.png!
> !jbds8b2-windows8.1-standard-user-private-install-was-able-to-update-via-central.png!
> ------
> However, there are problems when using an Admin user-installed shared install folder for JBDS.
> Steps to repro:
> *As nboldt / admin user* 
> * install JBDS 8.0.0.Beta2 (B104) into W:\shared-install\jbdevstudio (using default ownership/permissions)
> *As dummy / standard user*
> * Log in
> * Launch the shared JBDS
> * Install something from Central
> !jbds8b2-windows8.1-standard-user-shared-install-was-able-to-install-into-shared-install-folder.png!
> *PROBLEM*: standard user should not be able to install new features into the shared install folder
> *As kid / child user*
> * Log in
> * Launch the shared JBDS
> * Noted that the suggested path for workspace was the one last used by *dummy user*, to which that user doesn't have read permission
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error.png!
> !jbds8b2-windows8.1-standard-user-shared-install-last-used-by-dummy-launched-by-kid-error2.png!
> *PROBLEM*: should default to current user's home dir, not another user's previous workspace selection



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)