Enabling TS 6.7.1 SSO causes submit workflow to fail

TeamSite 6.7.1 + patch 1
Red Hat Linux 4.4

After enabling SSO, I am no longer able to use the submit workflow. I am getting a popup that says:

Invalid workflow:
ERROR:02419: Wrong username/password

The following is logged for this problem:


2007-02-24 16:42:53,845 ERROR com.interwoven.log100.impl.Log4JLogger : error - doIsPermitted: An CSException occurred when checking isPermitted on
---
com.interwoven.cssdk.filesys.impl.CSSimpleFileImpl{
name=wft_opendeploy.cfg
creationDate=Sat Feb 24 16:40:13 CST 2007
owner=xo3058
group=tsadmin
permissions=rwxrwxr-x
locked=true
lockComment="Locked by launching edit."
lockOwner=xo3058
lockCreator=xo3058
lockAreaVPath=//teamsited03/default/main/admin/TeamSiteConfig/WORKAREA/ServerSettings
lockCreationDate=Sat Feb 24 16:38:56 CST 2007
contentModificationDate=Sat Feb 24 16:40:13 CST 2007
attributeModificationDate=Sat Feb 24 16:40:13 CST 2007
kind=1
contentKind=20
modified=true
lastModifier=xo3058
readable=true
writable=true
privateToWorkarea=false
vpath=//teamsited03/default/main/admin/TeamSiteConfig/WORKAREA/ServerSettings/local/config/wft/solutions/wft_opendeploy.cfg
size=3103
revisionString=/main/admin/TeamSiteConfig/6+
revisionComment=
revisionNumber=6
revisionBranch=//teamsited03/default/main/admin/TeamSiteConfig
}
---

com.interwoven.cssdk.filesys.CSObjectAlreadyExistsException: //teamsited03/default/main/admin/TeamSiteConfig/WORKAREA/ServerSettings/local/config/wft/solutions/wft_opendeploy.cfg : LockFile(Item already exists)
        at com.interwoven.cssdk.filesysauth.jni.FileSysAuthServiceAdapterImpl.isPermitted(Native Method)
        at com.interwoven.cssdk.filesys.impl.CSNodeImpl.isPermitted(CSNodeImpl.java:123)
        at com.interwoven.cssdk.filesys.impl.CSFileImpl.isPermitted(CSFileImpl.java:1382)
        at com.interwoven.ui.teamsite.auth.CSAuthorizationManager.doIsPermitted(CSAuthorizationManager.java:471)
        at com.interwoven.ui.teamsite.auth.CSAuthorizationManager.doIsPermitted(CSAuthorizationManager.java:403)
        at com.interwoven.ui.teamsite.auth.CSAuthorizationManager.isPermittedForComposite(CSAuthorizationManager.java:327)
        at com.interwoven.ui.teamsite.auth.CSAuthorizationManager.isPermitted(CSAuthorizationManager.java:67)
        at com.interwoven.ui.base.auth.AuthorizationManager.isPermitted(AuthorizationManager.java:177)
        at com.interwoven.ui.base.widget.Widget.doPermissionCheck(Widget.java:670)
        at com.interwoven.ui.base.widget.Widget.doPermissionCheck(Widget.java:568)
        at com.interwoven.ui.base.widget.MenuTag.merge(MenuTag.java:359)
        at com.interwoven.ui.base.widget.MenuTag.(MenuTag.java:91)
        at com.interwoven.ui.base.widget.ActionListTag.merge(ActionListTag.java:274)
        at com.interwoven.ui.base.widget.Widget.loadConfig(Widget.java:831)
        at com.interwoven.ui.base.widget.Widget.doStartTag(Widget.java:413)
        at com.interwoven.ccpro.filesys.area_005fnavigation.lists.list_005fdirectory_jsp._jspService(list_005fdirectory_jsp.java:1234)
        at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
        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 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672)
        at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463)
        at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398)
        at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)

I am going to file a support case as I assume this is some sort of bug.

Find more posts tagged with

Comments

jkm

You are enabling SSO using siteminder or some different product?

Did someone else find any issues with TS6.7.1 and siteminder6 integration?

We are planning to implement this shortly but if someone faced any particular issues with this implemenaton then will be very happy to know at this stage so that we can think upon appropriate workarounds earlier rather than pulling our hair while implementing.

Bill Klish

This is using Sun Access Manager and their suite of products. There is a known bug with SSO and TeamSite 6.7.1 where response headers aren't working. The work around is to use cookies instead. However, it appears that even with that there is still some sort of problem.

I will update this thread if/when I hear from support.

ReggieRWalker

Bill,

Did you ever get any resolution with this issue?

Reggie

nipper

Did you ever get any resolution with this issue?

It is supposed to be fixed in the SP released for 6.7.1.

Download it and see.

Bill Klish

This is an error in every one of the CLTs that TeamSite uses. Something about a library that was problematic, but included in all of the CLTs. We were issued a black patch which has solved the issue and I told a tested patch should be coming out shortly which will address this issue.