This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 168106 - Cannot login to Kenai with correct credentials
Summary: Cannot login to Kenai with correct credentials
Status: RESOLVED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Team Framework (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Jan Becicka
URL:
Keywords:
: 165606 166850 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-07-03 23:56 UTC by liono
Modified: 2010-05-26 15:20 UTC (History)
8 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NB 6.7 logfile (35.00 KB, text/plain)
2009-07-03 23:57 UTC, liono
Details
Screenshot of NB 6.7.1 on Ubuntu LTS logged onto Kenai. (153.37 KB, image/jpeg)
2009-08-08 00:01 UTC, liono
Details

Note You need to log in before you can comment on or make changes to this bug.
Description liono 2009-07-03 23:56:00 UTC
Environment: Ubuntu Linux 8.04 LTS, Sun JDK 1.6u12 (1.6.0_12-b04), Netbeans 6.7 SE version.

After doing several tests I came to the conclusion that the Kenai plugin is somehow being influenced by the installation
of any EE (related) plugin. As soon as one of these plugins is installed (or to put it even simpler: as soon as you can
detect Glassfish or other EE servers under the "servers" tab in the services window) then it becomes impossible to logon
to Kenai. Even though you're using the correct credentials.

I came to this conclusion after many tests.. At first I suspected this behavior to be linked with importing settings
from a previous version until I realized that I allowed some modules to get transferred as well. I then started working
from a situation without any plugins but the default and started installing some. I then realized that as soon as I
tried to install the "Mobility End to End" plugin things stopped working.

Then I realized that this plugin is depending on some EE related plugins (Identity management, java web applications,
etc). So this evening I went back to my saved settings in which I had installed all plugins I need and where I couldn't
logon to Kenai. I then started de-installing all EE (related) plugins one by one and just when I couldn't see any
entries under the "servers" tab (none but Ruby related entries) the connection to Kenai suddenly succeeded all of a sudden.

"Mobility End to End" depends on 4 plugins: Identity Management, Java Web Applications, Mobility and SOAP Web Services.
If you try to install any of the EE related plugins it will automatically select the others as well (they depend on each
other as well) with the inevitable result that you can't logon to Kenai anymore. I've tested this several times and
can't discover any inconsistent behavior.

Note that this problem doesn't seem to appear on Windows. At least I didn't got any errors when performing the same
steps as mentioned above.

Logfile is attached. I marked this P2 because this problem is severely hindering Kenai usage on Linux. Better put;
rendering it totally unuseable.
Comment 1 liono 2009-07-03 23:57:17 UTC
Created attachment 84351 [details]
NB 6.7 logfile
Comment 2 Milan Kubec 2009-07-07 09:12:36 UTC
Please evaluate. Thanks.
Comment 3 Jan Becicka 2009-07-08 12:57:42 UTC
anyone else is able to reproduce this?
Comment 4 Jan Becicka 2009-07-17 06:48:25 UTC
joshis, juhrik - please try to reproduce. Thanks

*** This issue has been marked as a duplicate of 166850 ***
Comment 5 Jan Becicka 2009-08-07 15:26:53 UTC
not a duplicate
Comment 6 Jan Becicka 2009-08-07 15:31:17 UTC
additional comment from Steve Roughton:
...
I read a forum message that someone deleted all their preferences and restarted, and his Kenai login worked, until he
registered appservers.
Interestingly, I just removed two remote active Glassfish appservers (leaving one remote appserver that is not currently
running), restarted NB, and my Kenai login worked. Then I re-registered the instances, restarted, and the login failed.
I switched to the Projects tab and restarted, and the Kenai login worked.  So... it seems to have something to do with
whether NB connects to those remote servers before I login to Kenai...
...

Comment 7 liono 2009-08-07 23:59:54 UTC
I'm not too sure that I agree that this wasn't a duplicate but even then I really don't think this is relevant anymore.
A good 2 weeks ago I upgraded to NetBeans 6.7.1 and Kenai just works. Same configuration, no changes with regards to JDK
versions or libraries and such; just moved from 6.7 to 6.7.1.

I even started my own project on Kenai; works like a charm. I'll attach a screenshot to prove my case here.
Comment 8 liono 2009-08-08 00:01:43 UTC
Created attachment 85988 [details]
Screenshot of NB 6.7.1 on Ubuntu LTS logged onto Kenai.
Comment 9 Jan Becicka 2009-08-11 12:08:21 UTC
reopen. reproducible
Comment 10 Jan Becicka 2009-08-11 12:09:06 UTC
*** Issue 166850 has been marked as a duplicate of this issue. ***
Comment 11 Jan Becicka 2009-08-11 12:45:26 UTC
>> With 6.7.1, I can login to Kenai until I click the "Services" tab and
>> open the "Servers" node.  Once NB establishes connections to remote
>> Glassfish servers registered, the Kenai plugin apparently loses its
>> connection to kenai.com.  I tried "Share Project on Kenai" and the
>> dialog box is unable to retrieve the list of licenses from the
>> server.  The Kenai dialog worked fine, until I clicked the Services tab.
>>
>> Weird!
>>
>> -Steve
Comment 12 Jan Becicka 2009-08-11 13:53:51 UTC
Debug output:

INFO [org.netbeans.modules.kenai.ui.LoginPanel]: Authentication failed
java.security.cert.CertificateException: The certificate chain from the server is not trusted
        at
com.sun.enterprise.admin.jmx.remote.https.SunOneBasicX509TrustManager.checkCertificate(SunOneBasicX509TrustManager.java:264)
        at
com.sun.enterprise.admin.jmx.remote.https.SunOneBasicX509TrustManager.checkServerTrusted(SunOneBasicX509TrustManager.java:141)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1027)
Caused: javax.net.ssl.SSLHandshakeException
        at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611)
        at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187)
        at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124)
        at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516)
        at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1139)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1123)
        at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:434)
        at
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:166)
        at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:904)
        at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:230)
        at org.netbeans.modules.kenai.RestConnection.connect(RestConnection.java:219)
Caused: java.io.IOException: Cannot connect to : kenai.com
        at org.netbeans.modules.kenai.RestConnection.connect(RestConnection.java:257)
        at org.netbeans.modules.kenai.RestConnection.post(RestConnection.java:182)
        at org.netbeans.modules.kenai.RestConnection.post(RestConnection.java:176)
        at org.netbeans.modules.kenai.KenaiREST.verify(KenaiREST.java:376)
Caused: org.netbeans.modules.kenai.api.KenaiException. Server response=
        at org.netbeans.modules.kenai.KenaiREST.verify(KenaiREST.java:378)
        at org.netbeans.modules.kenai.api.Kenai.login(Kenai.java:156)
        at org.netbeans.modules.kenai.ui.spi.UIUtils$2$1.run(UIUtils.java:208)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1070)
[
[
  Version: V3
  Subject: CN=kenai.com, OU=Class B, O=Sun Microsystems Inc, L=Menlo Park, ST=California, C=US
  Signature Algorithm: SHA1withRSA, OID = 1.2.840.113549.1.1.5

  Key:  Sun RSA public key, 1024 bits
  modulus:
121328194123119634322747939080224869982764698333896358915936424648636925644804314343380571315966354140959639994712735746577236565737997823167119188961916872920701083545952803018912745932889873996789038338289189511250347710614077898431472357464153730588027257839302408870178671613594837826033230746314830235303
  public exponent: 65537
  Validity: [From: Wed Oct 08 02:00:00 CEST 2008,
               To: Sun Oct 09 01:59:59 CEST 2011]
  Issuer: CN=Sun Microsystems Inc SSL CA, OU=Class 3 MPKI Secure Server CA, OU=VeriSign Trust Network, O=Sun
Microsystems Inc
  SerialNumber: [    70d05569 265d458a af9d798a d1272a55]

Certificate Extensions: 8
[1]: ObjectId: 2.5.29.14 Criticality=false
SubjectKeyIdentifier [
KeyIdentifier [
0000: CF 16 2B C4 40 A9 9F B4   66 EC A2 E3 88 B7 01 90  ..+.@...f.......
0010: ED 7B CB DD                                        ....
]
]

[2]: ObjectId: 2.5.29.35 Criticality=false
AuthorityKeyIdentifier [
KeyIdentifier [
0000: D7 DD 5E 81 BE CF 5C E3   DC D2 F2 8D ED 04 B8 AC  ..^...\.........
0010: 17 F9 01 FA                                        ....
]

]

[3]: ObjectId: 2.5.29.31 Criticality=false
CRLDistributionPoints [
  [DistributionPoint:
     [URIName: http://SVRC3SecureSunMicrosystems-MPKI-crl.verisign.com/SunMicrosystemsIncClassBUnified/LatestCRLSrv.crl]
]]

[4]: ObjectId: 2.5.29.32 Criticality=false
CertificatePolicies [
  [CertificatePolicyId: [2.16.840.1.113733.1.7.23.3]
[PolicyQualifierInfo: [
  qualifierID: 1.3.6.1.5.5.7.2.1
  qualifier: 0000: 16 1C 68 74 74 70 73 3A   2F 2F 77 77 77 2E 76 65  ..https://www.ve
0010: 72 69 73 69 67 6E 2E 63   6F 6D 2F 72 70 61        risign.com/rpa

]]  ]
  [CertificatePolicyId: [2.16.840.1.113536.509.3647]
[PolicyQualifierInfo: [
  qualifierID: 1.3.6.1.5.5.7.2.1
  qualifier: 0000: 16 1B 68 74 74 70 73 3A   2F 2F 77 77 77 2E 73 75  ..https://www.su
0010: 6E 2E 63 6F 6D 2F 70 6B   69 2F 63 70 73           n.com/pki/cps

], PolicyQualifierInfo: [
  qualifierID: 1.3.6.1.5.5.7.2.2
  qualifier: 0000: 30 27 1A 25 56 61 6C 69   64 61 74 65 64 20 46 6F  0'.%Validated Fo
0010: 72 20 53 75 6E 20 42 75   73 69 6E 65 73 73 20 4F  r Sun Business O
0020: 70 65 72 61 74 69 6F 6E   73                       perations

]]  ]
]

[5]: ObjectId: 2.5.29.37 Criticality=false
ExtendedKeyUsages [
  serverAuth
  clientAuth
]

[6]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
  DigitalSignature
  Key_Encipherment
]

[7]: ObjectId: 1.3.6.1.5.5.7.1.1 Criticality=false
AuthorityInfoAccess [
  [accessMethod: 1.3.6.1.5.5.7.48.1
   accessLocation: URIName: http://ocsp.verisign.com]
]

[8]: ObjectId: 2.5.29.19 Criticality=false
BasicConstraints:[
  CA:false
  PathLen: undefined
]

]
  Algorithm: [SHA1withRSA]
  Signature:
0000: 35 19 E8 DB 32 53 A3 92   D2 2A E1 B8 59 B8 2F 53  5...2S...*..Y./S
0010: C6 B6 35 0A 98 DF F2 8A   26 CB 88 6C E1 94 78 B8  ..5.....&..l..x.
0020: 9A 0C EA 50 39 21 19 F9   AF 05 30 DD CD 1B CA BD  ...P9!....0.....
0030: EF AC 36 D2 3C EF 66 FA   4D 5D 0E 01 33 51 46 5B  ..6.<.f.M]..3QF[
0040: 39 13 F8 FE EA 72 7E 53   EB 6C B1 83 65 94 3F 66  9....r.S.l..e.?f
0050: 76 59 A5 03 59 FB 03 F2   F9 6A D1 77 7C E7 D6 E4  vY..Y....j.w....
0060: 04 59 53 00 DF A5 B6 07   56 8B 50 FC 07 D1 B3 E2  .YS.....V.P.....
0070: 04 4E 87 91 FB 41 7F 52   75 AD 1F DD 43 24 94 3B  .N...A.Ru...C$.;
0080: 5B E6 77 C5 1F EE 52 24   6E 3C CE D3 86 D5 A7 D4  [.w...R$n<......
0090: 0A E9 9C 08 B0 BB 46 59   44 18 FD 05 21 76 FD 8A  ......FYD...!v..
00A0: 3F 42 AF 68 78 0F 08 8E   DA FA A8 BF BA 47 21 85  ?B.hx........G!.
00B0: CF FE C3 E7 8A 0B 9B 8E   73 1C 4B 8B A9 0E 73 96  ........s.K...s.
00C0: 69 0B 9A DA AC 80 7C 86   72 EC 66 1F BF B2 22 D4  i.......r.f...".
00D0: 33 13 4A 66 76 D1 E4 B9   40 65 2C C3 56 B3 7F 2F  3.Jfv...@e,.V../
00E0: 9E 43 D7 7D E0 B3 31 DF   37 36 2C 60 8C 0C CA CA  .C....1.76,`....
00F0: 32 CA 9D 3B 57 EF EB F0   FF F4 A3 39 3D 92 F8 38  2..;W......9=..8

]
Comment 13 Jan Becicka 2009-08-11 13:59:20 UTC
It looks like there is some problem with certificates. Starting of glassfish somehow change handling of ssl certificates.
pcw, vkraemer, do you have any idea?
Comment 14 Jan Becicka 2009-08-11 15:18:14 UTC
fixed in http://hg.netbeans.org/cdev/rev/0ef9f954c627

candidate for patch?
Comment 15 Petr Dvorak 2009-08-11 15:26:32 UTC
Definitely... added a flag to the status whiteboard.
Comment 16 Quality Engineering 2009-08-12 06:29:03 UTC
Integrated into 'main-golden', will be available in build *200908120201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/0ef9f954c627
User: Jan Becicka <jbecicka@netbeans.org>
Log: #168106: Cannot login to Kenai with correct credentials
Comment 17 Jaromir Uhrik 2009-09-18 16:19:48 UTC
*** Issue 165606 has been marked as a duplicate of this issue. ***
Comment 18 roti 2010-05-26 14:56:00 UTC
Just installed nb 6.9 rc1, and the problem raised again.

I can login with browser, but not from nb:


INFO [org.netbeans.modules.kenai.ui.LoginPanel]: Authentication failed
SASL authentication failed using mechanism PLAIN: 
        at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java:325)
        at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:395)
        at org.netbeans.modules.kenai.api.Kenai.xmppConnect(Kenai.java:695)
        at org.netbeans.modules.kenai.api.Kenai.login(Kenai.java:289)
        at org.netbeans.modules.kenai.ui.spi.UIUtils$1$1.run(UIUtils.java:233)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1957)
Caused: org.netbeans.modules.kenai.api.KenaiException. Server response=
        at org.netbeans.modules.kenai.api.Kenai.xmppConnect(Kenai.java:699)
        at org.netbeans.modules.kenai.api.Kenai.login(Kenai.java:289)
[catch] at org.netbeans.modules.kenai.ui.spi.UIUtils$1$1.run(UIUtils.java:233)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
        at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1957)
Comment 19 Jan Becicka 2010-05-26 15:03:03 UTC
roti, are you able to use chat in web browser(not just login to kenai)?  Thanks
Comment 20 roti 2010-05-26 15:20:24 UTC
Sorry, I do not have a project. So it is ok.