Allowed Tag Issue in templating.cfg

Hi All
In templating.cfg we are configuring a datatype for no access to author as mentioned below.

When we select "New Form" entry an error is thrown. But when we edit DCR already created by an editor, teamsite allows us to edit the dcr and save it. This is applicable for group, user as well.

This is very critical.

Any help in this regard is very much appreciated.

Environment:
Teamsite 6.7.1 SP1
Solaris 10

Thanks & Regards,
Karthik

Find more posts tagged with

Comments

Bhargav Coca

I know this is may not be the case, but did you do an iwreset after setting the templating.cfg? please do it and then see if it works.

Thanks

nipper

I know this is may not be the case, but did you do an iwreset after setting the templating.cfg? please do it and then see if it works.

Thanks

You do not need an iwreset after changing templating.cfg. The templating.cfg is read on every open of a template.

Adam Stoller

Hi All
In templating.cfg we are configuring a datatype for no access to author as mentioned below.
<allowed><not><cred role="author"/></not></allowed>
When we select "New Form" entry an error is thrown. But when we edit DCR already created by an editor, teamsite allows us to edit the dcr and save it. This is applicable for group, user as well.

This is very critical.

Any help in this regard is very much appreciated.

Environment:
Teamsite 6.7.1 SP1
Solaris 10

Thanks & Regards,
Karthik

What is the "error"?
Are there any forms that Author's are allowed to create?
If not - that would explain it - Author's cannot use New Form - because that's how you configured it.

kkrathi

Posting the message on behalf of karthik.

The requirement in this case is not to allow the author to create or edit the DCRs for a particular datatype. For other data types author is able to create, since we did not give any restrictions. Please note that we have not modified the default roles.xml file.

There is error thrown when he selectes "New Form" which is correct. But when he modifies the DCR created by valid user, he is able to modify the DCR and no error is thrown.

In the manual, it is mentioned that if we set the allowed tag to for a particular role, the data type itself will not be visible. But in this case it is visible and the author is able to edit the DCR as well.

The permissions we have set for entire templatedata directory is 775.

Thanks & Regards,
Krishna
Teamsite 6.7.1 SP1
Solaris 10

Adam Stoller

Posting the message on behalf of karthik.

The requirement in this case is not to allow the author to create or edit the DCRs for a particular datatype. For other data types author is able to create, since we did not give any restrictions. Please note that we have not modified the default roles.xml file.

There is error thrown when he selectes "New Form" which is correct. But when he modifies the DCR created by valid user, he is able to modify the DCR and no error is thrown.

In the manual, it is mentioned that if we set the allowed tag to for a particular role, the data type itself will not be visible. But in this case it is visible and the author is able to edit the DCR as well.

The permissions we have set for entire templatedata directory is 775.

Thanks & Regards,
Krishna
Teamsite 6.7.1 SP1
Solaris 10

Where is the user navigated to within the workarea when they attempt to run New Form?
If they're navigated within the templatedata/category/data-type directory - NewForm will automatically attempt to initiate a new form of that category/data-type - so that might be the issue.

Also - are you / then using prune-missing-files="t" in the templating.cfg or are they using regex's to define which template types are available for which branches?

I haven't had to deal with restricted access for templates in a while (if at all, now that I think about it) - so I'm not sure what else to consider - but having more information about the context in which these errors occur and what the actual error message is - would probably help.

CrosstabCalendarLayout.rptdesign

Karthik_SP

Environment:
Teamsite 6.7.1 SP1
Solaris 10

We are using regex to define which template types are available for which branches.

User navigates to the category/datatype and then selects new form entry and the error thrown is,
=======================================================
Error:A problem was encountered trying to read the datacapture.cfg file for type ProductDetails. Please contact your system administrator.
Root cause:
null

Details...

java.lang.NullPointerException
at com.interwoven.ui.formspub.utils.TemplateManagerImpl$UserFilter.isTypeAllowed(TemplateManagerImpl.java:1023)
at com.interwoven.ui.formspub.utils.TemplateManagerImpl.isTDTAllowedInPath(TemplateManagerImpl.java:747)
at com.interwoven.ui.formspub.datacapture.NewDCRCommand.execute(NewDCRCommand.java:312)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommand(CommandHandler.java:419)
at com.interwoven.ui.base.impl.command.CommandCallbackContextImpl.callback(CommandCallbackContextImpl.java:45)
at com.interwoven.ui.base.wizard.WizardCommand.execute(WizardCommand.java:115)
at com.interwoven.ui.base.impl.command.CommandHandler.doExecuteCommand(CommandHandler.java:915)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandDescriptor(CommandHandler.java:752)
at com.interwoven.ui.base.impl.command.CommandHandler.tryRunCommandID(CommandHandler.java:629)
at com.interwoven.ui.base.impl.command.CommandHandler.runCommandLoop(CommandHandler.java:234)
at com.interwoven.ui.base.impl.command.CommandServlet.doGet(CommandServlet.java:163)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.impl.auth.AuthenticationFilter.doFilter(AuthenticationFilter.java:204)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.interwoven.ui.base.util.SetRequestEncodingFilter.doFilter(SetRequestEncodingFilter.java:105)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)

========================================================

If the tries to edit the existing dcr, then he is able to edit.

We have tested the same scenario in TS6.5 SP2 (Solaris) and Allowed tag is working as per requirement.

We searched in TS6.7.1SP1 Release notes, this is not listed in open issues also.

Regards
Karthik

Adam Stoller

Environment:
Teamsite 6.7.1 SP1
Solaris 10

We are using regex to define which template types are available for which branches.

User navigates to the category/datatype and then selects new form entry and the error thrown is,
[...]
If the tries to edit the existing dcr, then he is able to edit.

We have tested the same scenario in TS6.5 SP2 (Solaris) and Allowed tag is working as per requirement.

We searched in TS6.7.1SP1 Release notes, this is not listed in open issues also.

Regards
Karthik

If your Author does not navigate into the category/datatype folder and does New Form - do they get an error? Do they see the potential for creating a form of the category/datatype that you don't want them to be able to create?

I believe this is a combination of user-training and filing a Bug/FR with IWOV Support. The user-training is to not navigate to the category/datatype first.
The Bug/FR is that the system should not throw an error in that circumstance

Karthik_SP

If he is not navigating to the data-type then he is not getting that data-type (not allowed).

But he is able to edit the dcr of that data-type.

Adam Stoller

If he is not navigating to the data-type then he is not getting that data-type (not allowed).

But he is able to edit the dcr of that data-type.

This merely confirms what I've already stated.
However, in re-reading the thread, I now realize that the issue wasn't the receiving of the (ungraceful) error upon navigating to the data-type directory and doing New Form, but rather the lack of error and permissibility of being able to edit a DCR of that same data-type which already exists.

The permissions we have set for entire templatedata directory is 775.

Have you tried setting the permissions to 770? (this is assuming the user is not a member of the group associated with the directory).

This could change my statement about this being a FR - it may entirely be a Bug (which should be reported to IWOV Support), but before you do that - can you verify that the user in question can only log in as Author as opposed to being able to login with multiple roles and just currently being logged in as Author?

If the latter is true - that might explain it - as TeamSite has a habit of allowing the least-restrictive role's abilities even when logged in with a more restrictive role (doesn't necessarily change it from being a Bug, but might qualify it a bit)

Karthik_SP

The particular user has been given only author role.
We have raised a support case and are awaiting reply for the same.

dynamicTestNew.rptdesign