-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
None
Spotted this problem while using the "jiraissues" macro in Confluence, to grab issues out from a JIRA which is integrated with Crowd.
It's found that the response doesn't contain any issues, i.e. <item/> elements, eventhough os_username and os_password parameters are provided. (See the line in = method.getResponseBodyAsStream() in com.atlassian.confluence.extra.jira.JiraIssuesMacro or access the URL via a browser with caching turned off)
This is what you'll see in JIRA:
klsupport@atlantis:/opt/atlassian-jira/3.7.3-ent_klsupport/bin$ 2007-05-09 11:21:20,735 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticato r] Logging off from Crowd 2007-05-09 11:21:20,736 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,736 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,756 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Invalidating user in Crowd-Seraph specific session variables 2007-05-09 11:21:20,756 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Invalidating user in Seraph specific session variables 2007-05-09 11:21:20,757 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Authenticating user with Crowd 2007-05-09 11:21:20,757 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,758 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,781 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,781 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,874 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,874 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,901 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Updating user session for Seraph 2007-05-09 11:21:20,902 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Request is not authenticated 2007-05-09 11:21:20,735 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Logging off from Crowd 2007-05-09 11:21:20,736 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,736 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,756 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Invalidating user in Crowd-Seraph specific session variables 2007-05-09 11:21:20,756 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Invalidating user in Seraph specific session variables 2007-05-09 11:21:20,757 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Authenticating user with Crowd 2007-05-09 11:21:20,757 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,758 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,781 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,781 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,874 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Connection URL: http://localhost:11002/crowd/services/SecurityServer 2007-05-09 11:21:20,874 http-11001-Processor24 DEBUG [service.soap.client.GenericClient] Using existing token: BbUHDf7FiMvcvi9b+H+Tew== 2007-05-09 11:21:20,901 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Updating user session for Seraph 2007-05-09 11:21:20,902 http-11001-Processor24 DEBUG [crowd.integration.seraph.CrowdAuthenticator] Request is not authenticated
It looks like it has something to do with the com.atlassian.crowd.integration.seraph.CrowdAuthenticator.
[CWD-314] Not able to Retrieve Issues (RSS) if JIRA is Integrated with Crowd
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510198 ] | New: JAC Bug Workflow v3 [ 3365483 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393127 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510198 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 273034 ] | New: Simplified Crowd Development Workflow v2 [ 1393127 ] |
| Workflow | Original: JIRA Bug Workflow v2 [ 174088 ] | New: Crowd Development Workflow v2 [ 273034 ] |
Justin Koke
made changes -
| Workflow | Original: jira [ 81208 ] | New: JIRA Bug Workflow v2 [ 174088 ] |
Justin Koke
made changes -
| Attachment | New: crowd-core-1.1.2-SNAPSHOT.jar [ 21945 ] | |
| Attachment | New: crowd-atlassian-user-1.1.2-SNAPSHOT.jar [ 21946 ] |
Justin Koke
added a comment - To apply the jar files as a patch for your current Crowd release (1.1.1), please do the following:
- Stop JIRA from running (ie. performing a shutdown of Tomcat)
- Move the following files from JIRA WEB-INF/lib : crowd-core-1.1.1.jar & crowd-atlassian-user-1.1.1.jar into a safe location, in-case you need to revert this patch.
- Replace the file you deleted above with the attached files.
- Restart JIRA
If you have any problems with these steps, please comment below.
Justin Koke
added a comment - To apply the jar files as a patch for your current Crowd release (1.1.1), please do the following:
Stop JIRA from running (ie. performing a shutdown of Tomcat)
Move the following files from JIRA WEB-INF/lib : crowd-core-1.1.1.jar & crowd-atlassian-user-1.1.1.jar into a safe location, in-case you need to revert this patch.
Replace the file you deleted above with the attached files.
Restart JIRA
If you have any problems with these steps, please comment below. Justin Koke
added a comment - Hi Nick,
1.1.2 will be release early next week. The changes for this issue just affect the client code, since there have been no interface changes to Crowd between 1.1.1 and 1.1.2 you should be able to use the newer client jars (1.1.2) against 1.1.1.
I will upload two SNAPSHOT jars that contain the patch, these will be marked crowd-core-1.1.2-SNAPSHOT.jar & crowd-atlassian-user-1.1.2-SNAPSHOT.jar
Since we are still testing these changes on our internal systems, please make sure that you keep a backup of the older JAR files if you see adverse behavior.
Regards,
Justin
Justin Koke
added a comment - Hi Nick,
1.1.2 will be release early next week. The changes for this issue just affect the client code, since there have been no interface changes to Crowd between 1.1.1 and 1.1.2 you should be able to use the newer client jars (1.1.2) against 1.1.1.
I will upload two SNAPSHOT jars that contain the patch, these will be marked crowd-core-1.1.2-SNAPSHOT.jar & crowd-atlassian-user-1.1.2-SNAPSHOT.jar
Since we are still testing these changes on our internal systems, please make sure that you keep a backup of the older JAR files if you see adverse behavior.
Regards,
Justin 
Nick Waanders
added a comment - Will this be available as a patch to 1.1.1 prior to the release of Crowd 1.2? If not, how far away is 1.2?
Nick
Nick Waanders
added a comment - Will this be available as a patch to 1.1.1 prior to the release of Crowd 1.2? If not, how far away is 1.2?
Nick 
I'm using crowd 1.1.2 and jiraissue works fine only if we provide the username and pass (hard coded). I would assume that if user exist on both jira and confluence there shouldn't be a need to enter a user name and pass but it should display cases based on your login (in confluence).
Any ideas?
Regards
Kushtrim