I am currently using the Eclipse Jira Plugin (Atlassian Jira Connector 3.0.6.v20120628). If I try to connect to my Jira repository, it always tells me, that my login credentials are not valid. Using a TCP/IP monitor I could see that the SOAP login request did not contain any password (in1 parameter):
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><ns1:login soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://soap.rpc.jira.atlassian.com"><in0 xsi:type="xsd:string">gerdaschemann</in0><in1 xsi:type="xsd:string"></in1></ns1:login></soapenv:Body></soapenv:Envelope>
Is this a bug? Or did I miss some settings?
BTW: I see the same behaviour when connecting to https://studio.atlassian.com
The message is "Unable to authenticate with repository. Login credentials invalid"
thanks for the fast reply. Yes I have marked the 'remember password' checkbox marked, although the dialogue always seems to forget this setting - the next time I open the Repository preferences it is checked "off" again (and the password empty). Maybe this is due to the "not yet validated" status?
And yes, I have temporarily enabled a proxy, to allow for session monitoring throught the eclipse built in TCP/IP monitor. But I see the same request/response using wireshark ... No password is set in the request, and the SOAP Result contains this fragment:
<faultcode>soapenv:Server.userException</faultcode><faultstring>com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.</faultstring><detail><com.atlassian.jira.rpc.exception.RemoteAuthenticationException xsi:type="ns1:RemoteAuthenticationException" xmlns:ns1="http://exception.rpc.jira.atlassian.com"/><ns2:stackTrace xmlns:ns2="http://xml.apache.org/axis/">com.atlassian.jira.rpc.exception.RemoteAuthenticationException: Invalid username or password.
The checkbox issue is suspicious. It should stay checked even if validation fails.
It might be a problem with your local secure storage. Eclipse uses it to store passwords in a secure way so they are not saved in plain text.
Can you find secure storage setting in your Eclipse, check the path and confirm if the user starting Eclipse has permissions to access and write the file?
It is known issue in the Mylyn - it does not return any error if Eclipse fails to save password to secure storage.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot