Any configuration changes need to be done in RTC 6.0.4 version with SSO enabled to use distributed SCM?
We are using CLM - RTC v6.0.4 ifix006
The application has SSO - Single Sign on enabled and using Websphere liberty.
Here we facing some issues in Distributed SCM.
We are trying to add the a component from one CCM server to stream in another server.
But we are getting error "Auth Error"
Is there any configuration change need to be done with respect to SSO configuration?
The log trace
!ENTRY com.ibm.team.filesystem.ide.ui 4 0 2018-01-18 15:05:05.219
!MESSAGE Auth error
!STACK 0
com.ibm.team.scm.common.InvalidAuthenticationTokenException: Auth error
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:369)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeExceptions(MarshallerUtil.java:339)
at com.ibm.team.repository.common.internal.marshal.util.MarshallerUtil.decodeFault(MarshallerUtil.java:304)
at com.ibm.team.repository.transport.client.RemoteTeamService.constructExceptionFromFault(RemoteTeamService.java:717)
at com.ibm.team.repository.transport.client.RemoteTeamService.executeMethod(RemoteTeamService.java:560)
at com.ibm.team.repository.transport.client.RemoteTeamService.invoke(RemoteTeamService.java:202)
at com.ibm.team.repository.transport.client.ServiceInvocationHandler.invoke(ServiceInvocationHandler.java:43)
at com.sun.proxy.$Proxy42.createWorkspace(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invokeServiceCall(ServiceInterfaceProxy.java:254)
at com.ibm.team.repository.client.internal.ServiceInterfaceProxy.invoke(ServiceInterfaceProxy.java:110)
at com.sun.proxy.$Proxy42.createWorkspace(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy$2.run(ScmServiceInterfaceProxy.java:170)
at com.ibm.team.repository.client.internal.TeamRepository$3.run(TeamRepository.java:1328)
at com.ibm.team.repository.common.transport.CancelableCaller.call(CancelableCaller.java:79)
at com.ibm.team.repository.client.internal.TeamRepository.callCancelableService(TeamRepository.java:1323)
at com.ibm.team.scm.client.internal.ScmClientLibraryContext.callCancelableService(ScmClientLibraryContext.java:71)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invokeCancelableService(ScmServiceInterfaceProxy.java:166)
at com.ibm.team.scm.client.internal.ScmServiceInterfaceProxy.invoke(ScmServiceInterfaceProxy.java:94)
at com.sun.proxy.$Proxy42.createWorkspace(Unknown Source)
at com.ibm.team.scm.client.internal.WorkspaceManager.createWorkspace(WorkspaceManager.java:1824)
at com.ibm.team.scm.client.internal.WorkspaceManager.createWorkspace(WorkspaceManager.java:1718)
at com.ibm.team.filesystem.ui.operations.JoinOperation.createWorkspace(JoinOperation.java:61)
at com.ibm.team.filesystem.ui.operations.JoinOperation.repositoryRun(JoinOperation.java:158)
at com.ibm.team.repository.rcp.ui.operations.RepositoryOperation.run(RepositoryOperation.java:43)
at com.ibm.team.repository.rcp.ui.operations.JobRunner.run(JobRunner.java:245)
at com.ibm.team.repository.rcp.ui.operations.JobRunner$1.run(JobRunner.java:63)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comments
Donald Nong
Feb 18 '18, 7:55 p.m.What type of SSO is it? LTPA SSO or JSA SSO? Has it ever worked (with an older version) before?
Chandrasekar Muthukrishnan
Mar 01 '18, 4:07 a.m.We have LTPA SSO type configured. This is the first time we are using the SSO. So we didn't try in earlier versions
Donald Nong
Mar 02 '18, 3:55 a.m.I suppose there should be two Auth Tokens in this use case, but I don't know whether product code handles it correctly. Please contact IBM Support.