Question

I am running an asp.net application (VS2008/.net 3.5) and when running it under VS in debug more it works fine.

It reads files and directories from a network share happily.

I can run “cleartool startview [dynamic view name]” ok, I can “cleartool mount [vob]” happily.

But if I try to test for the existance of a file within the vob it can’t see it.

So I tried something different, I now run “cleartool ls -short -vob_only [filename]” to test for existance.

For both of those it works fine running under VS2008 but won’t work when running under IIS post deployment.

I have the set and the user has valid access to ClearCase.

Any ideas?

Answer 1

I found the problem and a resolution to this. The problem is that ClearCase is using the process user for authentication whereas the shared drive access mentioned in the original question is using the thread user.

The reason for this is the when accessing ClearCase it spawns off a new process – and child processes always use the parents process security context and not the current thread’s.

The way around this was to run the web application within its own application pool which is running as a user with rights to access ClearCase. An inflation of rights beyond what should be really necessary however it did the trick.