Restriction to JSP for author/editor

Hi all,
My requirement is like this:
The requirement for our project is to restrict the Editors and authors
from accessing the JSPs, The JSP directory should appear as hidden.
The JSPs are present under a direcory named JSP at the hierarchy of
templatedate. How can we implement this?

The JSPs are created on the fly. If the author/Editor creates a new DCR
and
generates the JSP then it should generate under JSP directory but the
author/ Editor should not able to look into that directory.

Please throw some light on this.
Thanks,
-Parag
TeamSite 6.7.1 Win2K3

Find more posts tagged with

Comments

cute_guy

Hi all,
My requirement is like this:
The requirement for our project is to restrict the Editors and authors
from accessing the JSPs, The JSP directory should appear as hidden.
The JSPs are present under a direcory named JSP at the hierarchy of
templatedate. How can we implement this?

The JSPs are created on the fly. If the author/Editor creates a new DCR
and
generates the JSP then it should generate under JSP directory but the
author/ Editor should not able to look into that directory.

Please throw some light on this.
Thanks,
-Parag
TeamSite 6.7.1 Win2K3

Is JSP directory existing under the workarea or the templatedata?

Is JSP directory a folder where generated JSP will be stored and is not a category/data type present in the templatedata folder?

Only branches and workareas can be hidden from users who don't have access to them by a setting in the iw.cfg

Do you want to restrict access of users to the JSP folders?

Did you try using different groups and permissions?

IF JSP is a category/datatype present inside the templatedata then authors/editors can be restricted access by making a cred configuration setting in the templating.cfg?

Did you try using cred option in the templating.cfg?

RajatChopra

Hi all,
My requirement is like this:
The requirement for our project is to restrict the Editors and authors
from accessing the JSPs, The JSP directory should appear as hidden.
The JSPs are present under a direcory named JSP at the hierarchy of
templatedate. How can we implement this?

The JSPs are created on the fly. If the author/Editor creates a new DCR
and
generates the JSP then it should generate under JSP directory but the
author/ Editor should not able to look into that directory.

Please throw some light on this.
Thanks,
-Parag
TeamSite 6.7.1 Win2K3

If everyone accesses a single workarea, then you need to create groups for the JSP users. Create a machine group for all the users who will have access to the JSP folder.

The second part of your requirement contradicts the first part. If they are able to create a DCR, Generate and place it in a directory, then why would you not want them to access the directory in which they generated it?? Doesn't sound right.

FYI, only branches and WorkAreas can be hidden. Not folders within a workarea. Another condition can be to use SUBMIT.cfg to grant access to certain groups to edit the JSP files, once they are submitted...

Parag

Thanks alot for reply!!!

The JSP dir is under the workarea but at the same level of templatedata
i.e. it is not a category/datatype.

I want to restrict the access to particular groups, Editor and Author only. Rest all can see into it.

We can not use the cred option in templating.cfg as it not a category/datatype.

User creates dcr, generates the SHTML page and thru the same presentation template the JSPs are created. As this is client requirement, they might want to keep the JSP generation hidden from the author.

Thanks,
-Parag

Adam Stoller

Thanks alot for reply!!!

The JSP dir is under the workarea but at the same level of templatedata
i.e. it is not a category/datatype.

I want to restrict the access to particular groups, Editor and Author only. Rest all can see into it.

We can not use the cred option in templating.cfg as it not a category/datatype.

User creates dcr, generates the SHTML page and thru the same presentation template the JSPs are created. As this is client requirement, they might want to keep the JSP generation hidden from the author.

Thanks,
-Parag

The submit.cfg option (along with group entries) is probably the simplest way you can restrict access to the files from other users.

If the author/editor is the one who performs the generation of the JSP - they need write access to the folder where the JSPs are stored - so the folder needs to be allow them write access, but the individual files can have their access changed on submit.

Alternatively, if all output generation is managed through a workflow - you could assign the owner of the task that performs the generation to an account that is not author/editor - and then you could protect the directory (and files) that are generated from being accessible by author/editor.

The likely problem with the first scenario is that if joe-author creates a new DCR and generates a new JSP from it - it will work, but then (after the JSP was submitted) if joe-author edits the DCR and tries to re-generate the JSP - it will likely fail because they no longer have access to touch/modify that output file.

Thus the alternative (workflow approach) is probably more likely to succeed.