Folks; ... about to try tracking down the PKIX path building error in our CAS environment, I feel having hit a wall. Setup:
- Both CAS and the main webapp to use CAS/SSO run inside a Glassfish v3.0.x application server running behind an apache2 reverse proxy. - The reverse proxy also provides HTTPS with a certificate signed by an official authority. - Glassfish v3 itself is connected to the reverse proxy using mod_jk. casServerName/Url/Prefix, in all cases, are the "public" domain name of our system, thus referring to the HTTPS service provided by the reverse proxy system. I followed the hints outlined in [1], including the "import trusted certificate" guide, importing, well, the signed domain certificate into the JRE keystore, ensured there's only one JAVA_HOME available to the application server - and still fail. So. What else can I do about this? Is there any way of tracking this down? Any way of figuring out more accurate debugging information? Could it be something specific to glassfishv3, in our setup? Any thoughts on that really appreciated. :) Thanks in advance, all the best. Kristian [1]https://wiki.jasig.org/display/CASUM/SSL+Troubleshooting+and+Reference+Guide -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
