can not login in Confluence, linked with Jira
Asked by Sam:

My Confluence suddenly failed to log in, but Jira was able to log in normally, and the environment was not adjusted.The user has logged in Confluence and can continue to use it as long as he does not log out, but if he logs out, he cannot log in again. The following error(s) occurred:

Sorry, your username and/or password are Sorry. Please try again.Re-add the Remote JIRA Directory to the Confluence user Directory menu.Report an error directly.Here are some error logs and information that have been processed for a long time without a solution.It was rebooted.

javax.xml.bind.UnmarshalException - with linked exception: \[org.xml.sax.SAXParseException; lineNumber: 78; columnNumber: 487; The reference to entity "collectorId" must end with the ';' delimiter.\] - with linked exception:  
\[org.xml.sax.SAXParseException; lineNumber: 78; columnNumber: 487; The reference to entity "collectorId" must end with the ';' delimiter.\]

<br />

at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:497)  
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.searchUsers(RestCrowdClient.java:557)  
at com.atlassian.crowd.integration.rest.service.RestCrowdClient.testConnection(RestCrowdClient.java:545)  
at com.atlassian.crowd.directory.RemoteCrowdDirectory.testConnection(RemoteCrowdDirectory.java:828)  
at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.testConnection(CrowdDirectoryServiceImpl.java:69)  
... 315 more  
Caused by: javax.xml.bind.UnmarshalException  
- with linked exception:  
\[org.xml.sax.SAXParseException; lineNumber: 78; columnNumber: 487; The reference to entity "collectorId" must end with the ';' delimiter.\]  
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:335)  
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:514)  
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:215)  
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190)  
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:241)  
at com.atlassian.crowd.integration.rest.service.RestExecutor$MethodExecutor.andReceive(RestExecutor.java:489)  
... 319 more  
Caused by: org.xml.sax.SAXParseException; lineNumber: 78; columnNumber: 487; The reference to entity "collectorId" must end with the ';' delimiter.  
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)  
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)  
at org.apache.xerces.impl.XMLErrorReporter.reportErro


Answers:
author: Shannon S
body: Hi Sam,

Welcome to Atlassian Community. It's nice to meet you.

Could you confirm with me the version of Jira and Confluence that you're running? Have you already tried removing and re-adding the link to Jira?

Regards,

Shannon

comments: author: Sam
body: Oh, thank you for coming to support me. We are here to buy licenses that cost a lot of money a few years ago. The current Jira version is 7.2.4 Confluence version is 5.10.1. Currently Jira is normal, Confluence cannot log in, and the system has not changed. When I tried to re-add the directory Atlassian Jira in the user management menu of Confluence, I tested the connection when the configuration was completed, and an error occurred  
javax.xml.bind.UnmarshalException-with linked exception: \[org.xml.sax.SAXParseException; lineNumber: 78; columnNumber: 487; The reference to entity "collectorId" must end with the ';' delimiter.\]  
We have a lot of important stuff in it, which makes our work very troublesome.


author: Shannon S
body: Hi Sam,

Thank you for confirming that information. Something sounds like it might be corrupt in your setup.

You'll want to take a deeper look at your Jira and Confluence server logs for any stack trace errors. Those errors will tell us what the issue is. You can share those logs with me here if you need help interpreting them.

You do need to upgrade your Jira and Confluence instances. Both your versions of Confluence and Jira have already reached [End of Life](https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html), but there have also been some security vulnerabilities announced in the past year for both. These vulnerabilities can cause your site to be compromised, so it's impertinent that you do that as soon as you can.

* Last spring, there were a pair of security vulnerabilities announced for Confluence: [Confluence CVEs and common questions](https://community.atlassian.com/t5/Confluence-articles/Confluence-CVEs-and-common-questions/ba-p/1062634)
* In addition, there were some security vulnerabilities announced for Jira in September: [Security Advisories for Jira family, September 2019](https://community.atlassian.com/t5/Jira-articles/Security-Advisories-for-Jira-family-September-2019/ba-p/1181819)

See [Upgrading Jira](https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html) and [Upgrading Confluence](https://confluence.atlassian.com/doc/upgrading-confluence-4578.html) for more details.

Regards,

Shannon


Tags: confluence-server

jira

server