6 replies to this topic

[ducman]

Plastic SCM 4.1.10.391

AD security

MSSQL 2012

Server install and working for administrator

new user specifically added to repository and workspace with all rights in Plastic

new user specifically added to dir\files rights

new user added integrated security MSSQL

 

Client session unable to connect to workspace with error:

 

"Access to the path 'c:\xxxxxx\.plastic\plastic.wktree' is denied

 

Please advise

[manu]

Hi!

 

it seems that the client can't access to the workspace due to permissions.

 

Grant all the permissions for your Plastic SCM workspace and the client will be able to start-up.

[ducman]

I can grant right to the new Repository but i can't find where to grant specific rights to a specific workspace.

 

AD user granted file permissions..

 

I'm new to Plastic SCM and as i see it, workspaces are shared enviroments for code development?

 

If i have several projects in the same repository i should be able to create new workspace for each project and assign specific developers to specific workspaces?

[ducman]

if i right mouse and run the Plastic GUI as administrator i can get the user into the Respository/Workspace..

 

its a workaround but a security issue

[manu]

Hi Ducman,

 

I mean, grant permission in your windows directories, it's an issue with the permissions on your "c:\xxxx" path. That's why if you start the GUI as Admin you solve the issue, the windows Administrator user is having the read and write permissions granted in that dir.

[ducman]

doesn't work.. i've granted the user full admin rights in ALL the development directories. still no joy..

user specifically added via Plastic for repository and workspace..

 

i failed to mention that we are running this under Win2k8 remote sessions..

 

AND if user creates new workspace using right mouse admin to open SCM i can't see the new workspace?

[manu]

Hi,

 

 

doesn't work.. i've granted the user full admin rights in ALL the development directories. still no joy..

 

It's still strange that the Windows Administrator account is able to read/write in the workspace path and a regular user (with the permissions granted as you said) not.

Can you try to create the workspace in a different location? Maybe the Desktop, just to test if your regular windows user is able to use that path.

 

At the end of the day the Plastic client is just a process that's started with a certain user, the IO operations made by the Plastic SCM client are done by the user that started the process so if the Administrator user can work it must be something related with the Windows security.

 

AND if user creates new workspace using right mouse admin to open SCM i can't see the new workspace?

 

Each windows/linux user has their own workspaces list, so, if you create one workspace with the admin user it's stored for the admin session. You will find the workspaces list inside a file called "plastic.workspaces", this file is located in the Local user directory (C:\Users\XXXXX\AppData\Local\plastic4). If you copy this file and you place it into the cm.exe location path ("C:\Program Files\PlasticSCM4\client" by default) all the system users will share the workspaces list.