: Subject nane of signer cert does not match issuer name of supplied cert chain

Hi Folks,

Last weekend our Portal Production server got some issue, related to the Certificate problem.

Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Subject nane of signer cert does not match issuer name of supplied cert chain
at com.ibm.jsse2.bx.a(bx.java:14)
at com.ibm.jsse2.by.a(by.java:147)
at com.ibm.jsse2.by.a(by.java:202)
at com.ibm.jsse2.w.a(w.java:206)
at com.ibm.jsse2.w.a(w.java:280)
at com.ibm.jsse2.v.a(v.java:184)
at com.ibm.jsse2.by.a(by.java:193)
at com.ibm.jsse2.by.l(by.java:257)
…
…

Just to share a abit…

If you find this error, you might need to check whether the Certificate that is installed at the server side valid (or even broken) or not. Be noticed that you will not know the validity of the certificate by using the browser to view certificate. This is seen only by the Java code.

Then, after replacing this certificate, our problem was solved.

Cheers!

How to enable the Lotus Connections to support other document extensions/types

This document explains how to enable the LC-Blogs to support additional document types

1. Change the “allowed extensions” in the Blogs Administration
2. Add the MIME Type to the default host in WAS Admin Console

See these images

Lotus Quickr – Missing Public Places tab and Working with Template link

Hi Folks,

I got headache when I installed the Lotus Quickr 8.1 into my machine, when suddenly I noticed that the “Public Places” tab and “Working with Template” link were missing.

 

com.ibm.websphere.ltpa.Realm=null

Hi Folks,

I just realized the reason why my Portal which is authenticated using WMM does not have realm name.

Lotus Quickr – Couldn’t find design note

After changing name of the Folders in the Lotus Quickr place, some feature might not work.

Implementing the Portal Single Sign-Out

Implementing the Portal Single Sign-On is the common, however implementing the Portal Single Sign-Out is not common. This article explains how we implement the Portal Single Sign-Out.

Use Authorized Signed SSL Certificate to IBM HTTP Server

To enable HTTPS access to front-end Web Server nodes running IBM HTTP Server 6.0, SSL certificates should be created, IHS configured to use SSL certificates and WAS configured for HTTPS traffic

These steps are useful if you want to use the self-signed SSL Certificate on IBM HTTP Server

Lotus Connections – Blogs – My Updates – 404 error

Blogs – My Updates – 404 error

This is a bug inside the MyUpdatesServlet Code

WebSphere Portal 6 and Portlets Performance Tuning

Hi Folks, I was almost fed up doing the WPS and Portlets performance tuning. However, I finally able to achieve the accepted number of concurrent users (around 1500) in the WPS 6 running on 2 Windows Intel boxes.

How to Achive Portal to Domino SSO of Different User Registries

The standard and out-of-the-box way to achieve WebSphere Portal and Lotus Domino Application Single Sign-on is by using LTPA Token key. This LTPA Token is a shared web-based key account recognized by IBM WebSphere and Lotus Domino systems that enable the WebSphere or Lotus based applications to trust each other.