Link to home
Start Free TrialLog in
Avatar of ITDharam
ITDharamFlag for United States of America

asked on

Lotus Sametime Network Install fails when using https:// install base

I've been working on this very frustration Sametime Standard deployment and I'm at the very end phase, and I can't get the network install files to work correctly.  I can run the standalone client and things are fine.

I've actually narrowed it down to not being able to use an HTTPS URL as defined in my download.properties file, I can switch to HTTP, and the install works perfectly.

OK, so the problem is HTTPS right?  Probably, but I can't figure out where.  I'm using a wildcard cert purchased from Netsol, and I can browse to files in the same path no issue, so I really can't see the problem here.

I clued into using http instead of https because of the following error in the install log

Unable to access site: "https://stweb.company.com/sametime/network-install/install.win/updateSite" [java.security.NoSuchAlgorithmException: SSLContext Default implementation not found: ]  **I've but in bogus hostname info...

I can use a browser to access https://stweb.company.com/sametime/network-install/install.win/updateSite/site.xml  I can view the SSL cert and it looks normal.

I'm including the full log for your perusing enjoyment, hostnames also muddled.
error-log-0.xml
SOLUTION
Avatar of Sjef Bosman
Sjef Bosman
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ITDharam

ASKER

So I think you're on to something.  I'm still working with IBM support but clearly they have no idea about this, i've been escalated to the folks in India so now things are going to go a little slower, but at least they are going somewhere.

Developers told support that I need to import my SSL cert into (.keystore.JCEKS.IBM_J9_VM.install) A little googling and I find references to this keystore, and the fact that you need to update it with your cert (not self signed), and then also sign all your .JAR files with that keystore.  I imported the cert, but they didn't mention signing the JAR files so I've pushed back to support to clarify the process.

Anyways, I'm updating the ticket so you know I haven't forgotten about this, and so that maybe someone who has some experience with signing Java/Eclipse modules with a JAVA keystore can interject and tell me what exactly needs to be done. (wishful thinking...but sometimes wishes do come true!)
I'll send the URL to a friend who might know more...
Just letting you know that I've still got an open PMR with IBM.  At the moment they are looking into importing certificates into the Java keystore, and how to sign the JAR files.  I don't get why this is so tough...
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
How odd... Thanks for closing the question!
While sjef_bosman was the right track, turns out this was a trick question and my support with IBM revealed that their product just isn't able to support HTTPS for this particular function.