nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Deployment Config file permissions

skip11

OD 5.6 Sol7

When using the "New" button in OD to create a new deployment xml, the file permissions are set after a save to root Smiley Surprised

ther 666. We find this insecure, and I'd like to know if anyone can tell me if there is a way to change this behaviour without custom scripting.

thanks,

Ralph Barger
Credit Suisse Financial Services
Zurich, Switzerland

Edited by skip on 12/03/03 03:15 AM (server time).

Find more posts tagged with

Comments

Migrateduser

I don't think there's a way to tell OpenDeploy what perms to apply to the newly created deployment config file. The ownership of the file is likely the user that the Base Server is running as.

You might want to consider opening a case with Tech Support and filing a feature request. Please include a description of the behavior you would like to see, including what aspects should be configurable.

Thanks.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

One thought about something to try...

Create a generic deployment config (with desired perms) that serves as a template for new ones. Then when you want to create a new config, open up the generic one and change its name before saving it.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com