Receiving an unexpected error when sign on with the client
Environment:
Jazz Server 1.0M6a Jazz client 0.6.0.I20080411-1100 RedHat rehl 4 latest fixes applied. WebSphere Application Sever (WsAS) 6.1.0.15 DB2 9.1.0.4 LDAP Authentication via blue groups configured and functioning. The following exception is thrown when attempting to create a repository connection to the Jazz server from the Jazz client: Invalid user id / password logging into 'jazzsandbox.rchland.ibm.com'. An unexpected error was caught invoking service "https://jazzsandbox.rchland.ibm.com/jazz/service/com.ibm.team.repository.common.internal.IRepositoryRemoteService": The server is requesting authentication even though we just authenticated successfully. Please check your server configuration. I am able to authenticate and run the following; https://localhost:9443/jazz/setup https://localhost:9443/jazz/admin However I can not authenticate via the Jazz client. I have the following bluegroups configured WST_JazzAdmins, WST_JazzDWAdmins, WST_JazzUsers, WST_JazzGuests The following LDAP configuration is implemented in the teamserver.properties com.ibm.team.repository.ldap.findUsersByUserIdQuery=mail\=?1 com.ibm.team.repository.ldap.baseGroupDN=ou\=bluepages,ou\=ibmgroups,o\=ibm.com com.ibm.team.repository.ldap.findGroupsForUserQuery=uniquemember\={USER-DN} com.ibm.team.repository.ldap.membersOfGroup=uniquemember com.ibm.team.repository.ldap.registryLocation=ldap\://<ldap>\:389 com.ibm.team.repository.ldap.groupMapping=JazzAdmins\=WST_JazzAdmins,JazzUsers\=WST_JazzUsers,JazzDWAdmins\=WST_JazzDWAdmins,JazzGuests\=WST_JazzGuests com.ibm.team.repository.ldap.baseUserDN=ou\=bluepages,o\=ibm.com I have also mapped my user to the roles under hte app in WsAS. My Userid was also added to the Jazz configuration per Step 2: Create Initial User and Configure Jazz Team Server for LDAP on https://jazz.net/wiki/bin/view/Main/ServerSetupForLdapConfigurationM6 This error makes no sense as I can signon to the Jazz server from the IHS server on port 80 and 443 as well as 9080 and 9443 without and issues from the browser even without hte bluegroups configured. I created the bluegroups to make sure that was not the issue. Any ideas as to why I am not able to access the server from the client? |
5 answers
|
One additional not The following error is issued in the SystemOut.log
00000026 SystemOut O 15:26:43,604 WARN .team.repository.servlet.AbstractTeamServerServlet - GET request for RPC service "com.ibm.team.repository.common.internal.IRepositoryRemoteService" is not supported. The request was made by user "644226897" from "9.10.116.79". 00000026 WebApp E [Servlet I have not found any hits on this exception. |
|
I also find it interesting that under http://localhost:9443/jazz/admin Advanced the property that is displayed is com.ibm.team.repository.service.internal.RepositoryRemoteService not com.ibm.team.repository.common.internal.IRepositoryRemoteService
as indicated in the exception thrown in the SystemOut.log. |
|
Also should this not be pulling port 9443 from the URI rather than being "https://jazzsandbox.rchland.ibm.com/jazz/service/com.ibm.team.repository.common.internal.IRepositoryRemoteService":
should it not be "https://jazzsandbox.rchland.ibm.com:9443/jazz/service/com.ibm.team.repository.common.internal.IRepositoryRemoteService": |
|
|
Did you ever successfully used "https://jazzsandbox.rchland.ibm.com/jazz/" to access your repo?
When that happens that uri will be cached in the client along with a unique id of the repo. If you access the same repo using a different uri like "https://jazzsandbox.rchland.ibm.com:9443/jazz/" may be because someone decided to change the port on the server, the client will decide that the two URIs are the same since the repo id is the same. Can you please try the following? - delete all you repo connections from the team artifacts navigator. Then restart Eclipse. - Try to use "https://jazzsandbox.rchland.ibm.com:9443/jazz/" to connect to the server. I am just speculating here. I have never seen this problem to me. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.