why is environment cleared for inline?

Why is the environment cleared before an inline is executed from within a DCT, so that only the four Interwoven environment variables are defined in the environment for my processes? It is a hassle to maintain the environment in the environment and then again in config files or whatever so that it can be redefined for inlines.

Is there a bug open on this issue?

Find more posts tagged with

Comments

Adam Stoller

I'm not entirely sure of the exact reason - but it may have been based on security precautions - since you are executing a script on the server from a browser....

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I think it is a bug - I think the security issue is in being able to run any script on the server, not whether that script can see environment variables (especially things like SystemRoot).

If it were a security issue I think Interwoven should be more concerned that any user with edit rights to the DCT could upload a script onto the Y: drive and execute any code as a priviledged user with an inline.

If this is for the customers who store database connection information in an environment variable I think that clearing the environment should be an option.