Skip to main content

Websphere 6.1 administrative security + self signed certificates

I installed websphere 6.1 and chose the default "enable administrative security". Once I finished my installation, I noticed I could not login under https://localhost:9043/admin/console. I got a message about a certificate not being trusted.


First I discovered, that I had renamed my machine, but that /etc/hosts still had old entries for 127.0.0.1. Because of that, my node and cell names were still deduced from the old machine name.
I fixed that and reinstalled.


At login I got the failure: invalid security certificate.
My browser did not trust the self signed certificate that the websphere server uses.


I did following to fix that:
  • In /bin, started keyman: sudo ./ikeyman.sh
  • Opened jks file under profiles/AppSrv01/etc/DummyClientTrustFile.jks, password is WebAS.
  • there I looked up the default_signer, and selected the extract option. I exported cert.arm as base64 ascii.
  • under firefox, preferences, advanced, view certificates I imported the CA certificate
  • I restarted firefox.
The url with localhost still did not work, but when I replaced localhost by the machine name, I got access to my adminconsole.


Small remark: the self signed certificate websphere generated is valid for a year. The certificate itself probably too.

Comments

Post a Comment

Popular posts from this blog

SSL handshake failed: Secure connection truncated

Got this problem on Ubuntu 9.10 and 10.10. svn co --username=xx https:/yy zz “SSL handshake failed: Secure connection truncated” According to this link bug-ubuntu The solution is: sudo apt-get install libneon27 cd /usr/lib/ sudo rm libneon-gnutls.so.27 sudo ln -s /usr/lib/libneon.so.27 libneon-gnutls.so.27
12 comments
Read more

Create a groovy console and bind to selenium

Required groovy files In the previous posting we defined the pom file that we need for our build environment. Now we will setup some groovy files to get selenium and groovy running interactively. ConsoleWaiter.groovy The idea of Groovy Console I found on some other sides. Honour goes for instance too: http://josefbetancourt.wordpress.com/tag/eclipse-2/ I copied some code of this, and put it under src/test/groovy/com/jankester/selenium/test/utils: package com.jankester.selenium.test.utils /** * File: ConsoleWaiter.groovy */ import groovy.lang.Binding; import groovy.ui.Console; /** * Provides a wrapper for the console. * * Based on source by John Green * Adapted from: http://www.oehive.org/files/ConsoleWaiter.groovy * Released under the Eclipse Public License * http://www.eclipse.org/legal/epl-v10.html * * I added methods to allow use from Java. * * The run() method launches the console and causes this thread * to sleep until the console's window is closed....
1 comment
Read more

Interactive selenium testing

The problem Location of elements When I started using selenium, I noticed that it is not easy to do it right. First you start with IDE, but you notice, that the IDE does not really record a lot. In a next step I added firebug, and started analyzing how the elements where to be located: either by tag, id, class etc. Junit testcase With this information I could then create my junit testcase: @Test public void testMapView() throws Exception { //assert that we cannot see submenu of MapCreator elem = driver.findElement(By.className(SeleniumConstants.MAP_SUB_MENU)); String style = elem.getAttribute("style"); assertTrue("Element must have style display off.",style.matches("display: none.*")); logger.debug("Located element " + SeleniumConstants.MAP_SUB_MENU); //find menu and click on mapview elem = driver.findElement(By.id(SeleniumConstants.MAP_CONTROL)); actions.moveToElement(elem).click().perform(); //assert su...
3 comments
Read more