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; } } }

OD targetFilesystem

rodigz

Hi there,

Need some ideas thanks in advance.

i have target folders . i have defined the folders in odreceivers.
1. /OD/tmp/sample1
2. /OD/tmp/sample2

Basically I want to restrict users from deploying other folders/files under tmp.

My concernt now my fileslist starts with sample1/text1.txt etc.
the result will be /OD/tmp/sample1/sample1/text1.txt
the result I want is /OD/tmp/sample1text1.txt

Any ideas the best approach?

thanks!

Find more posts tagged with

Comments

ISCBorisB

Hi there,

Need some ideas thanks in advance.

i have target folders . i have defined the folders in odreceivers.
1. /OD/tmp/sample1
2. /OD/tmp/sample2

Basically I want to restrict users from deploying other folders/files under tmp.

My concernt now my fileslist starts with sample1/text1.txt etc.
the result will be /OD/tmp/sample1/sample1/text1.txt
the result I want is /OD/tmp/sample1text1.txt

Any ideas the best approach?

thanks!

Try to shorten target File System area(target root) in your Deployment configuration so that the full path belongs to
"allowedDirectories". Like that: <targetFilesystem area="/OD/tmp"/>. Either it will work or not depends on OD Engine
validation order: if it checks dynamically on *Full Path* basis you should be Ok

rodigz

good point but it will allow users to deploy anything under /OD/tmp

i want to limit two folders only:
/sample1 and /sample2

ISCBorisB

good point but it will allow users to deploy anything under /OD/tmp

That's not true. Remember, I'm not talking 'odreceiver' Files. That should stay the way you've already coded it.
My suggestion is to shorten "Target Deploy Root" in OD Configuration - the one you supply to 'iwodcmd start' command
[html]
. . .

. . .

[/html]

rodigz

yes. I did that.
In OD receivers, I've just declare the following as allowed folders.
allowedDirectories
path name="/apps/interwoven/OpenDeployNG/tmp"/
path name="/apps/interwoven"
path name="/OD/tmp/sample1"
path name="/OD/tmp/sample2"
allowedDirectories
correct right? Not working

ISCBorisB

yes. I did that.
In OD receivers, I've just declare the following as allowed folders.
allowedDirectories
path name="/apps/interwoven/OpenDeployNG/tmp"/
path name="/apps/interwoven"
path name="/OD/tmp/sample1"
path name="/OD/tmp/sample2"
allowedDirectories
correct right? Not working

What does "not working" mean? What is the issue manifestation? If you want help, post OD Conf and File list, I'll take a look

rodigz

Error that I'm getting
17:07:55 ERROR: [/OD/tmp] is not an allowed deployment path.

See attached config files

thanks!

ISCBorisB

Error that I'm getting
17:07:55 ERROR: [/OD/tmp] is not an allowed deployment path.

See attached config files

thanks!

1. Unless it's a typo, you have a problem here: <path name="="/OD/tmp/sample2"/>
2. Remove "doDeletes". It's rearly a good idea with File list and in this special case it implies that you are deleting from OD/tmp subfolders you did not deploy to
3. Note that date comparison is ignored for File list deployment
4. Can you post a File list?

rodigz

yes that's a type.
my filelist will be like this.
sample1/Computers/Desktops/testfile.html

rodigz

so this scenario works in your end.?
It will be great if you can try it in your test server.
thanks!

ISCBorisB

yes that's a type.
my filelist will be like this.
sample1/Computers/Desktops/testfile.html

Have you tried it without doDeletes? Access violation can be caused by deletion attempt as well as writing.
Still, it's possible that OD checks configuration upfront. In this case you'll have to massage your File list, I do not see any alternative.

rodigz

thanks for your suggestions. Yah it will be pain a abit if I modify the way I construct my filelist, need to do checking.

ISCBorisB

thanks for your suggestions. Yah it will be pain a abit if I modify the way I construct my filelist, need to do checking.

I've tested my own suggestion on Dev Server, worked flawlessly.

"allowedDirectories" fragment: <path name="d:/temp1/boris"/>
fl.txt contains single line: boris/test.txt

[html]

[/html]Your problem must be either "doDeletes" or perhaps you have File List entries that force OD to write under tmp.

rodigz

weird ... not working in my end..
same error not allowed directory.
can u please attached your odreceiver.xml

thanks!

Adam Stoller

weird ... not working in my end..
same error not allowed directory.
can u please attached your odreceiver.xml

thanks!

There are (at least) three parts to the equation:

parts of the equation.

samplereport_1.rptdesign

ISCBorisB

The use of doDeletes with filelist deployments is generally "good practice" and will tend to be far less problematic that using it with comparison deployments - but that's neither here nor there with respect to the question that was asked.

General "doDeletes" practice aside, this case is somewhat special. Let's say we have /OD/tmp/abc.txt File and deploy with the list that contains only "sample1/..." entries.
Providing that target area is /OD/tmp with "doDeletes" on OD engine will try to delete abc.txt and fail since /OD/tmp is not "Allowed Directory". I'm not sure if deletion failure
will cause transactional deployment failure but that seems logical

Adam Stoller

General "doDeletes" practice aside, this case is somewhat special. Let's say we have /OD/tmp/abc.txt File and deploy with the list that contains only "sample1/..." entries.
Providing that target area is /OD/tmp with "doDeletes" on OD engine will try to delete abc.txt and fail since /OD/tmp is not "Allowed Directory". I'm not sure if deletion failure
will cause transactional deployment failure but that seems logical

Huh?
Are you saying that /OD/tmp/abc.txt exists, or that /OD/tmp/abc.txt is in the filelist to be deployed?

In either case - if anything attempts to deploy or delete a file outside the allowed path, it should trigger and error - and if it's a transactional deployment it should trigger a rollback.

The point I was trying to make is that most of the thread was trying to focus on one or two variables - but you need to focus on all three variables (allowed path, target area, and path specifications in file list) in order to be able to try to diagnose the problems.

ISCBorisB

Huh?
Are you saying that /OD/tmp/abc.txt exists, or that /OD/tmp/abc.txt is in the filelist to be deployed?

No. The point I was trying to make was that "doDeletes" setting is relevant to the scenario under consideration.
If it is set to "Yes" OD will try to perform Deletion from /OD/tmp down the tree which (depending on the asset path) may be not allowed