I am having a problem with configuring CAS 3.1.3 on Websphere 6.1.
I believe the problem has to do with the SSL keys. I deploy on tomcat
successfully.
When deploying on WebSphere, the callback URL is not being hit. It gives me the
standard
...
...
Caused by: error.authentication.credentials.bad
at
org.jasig.cas.authentication.handler.BadCredentialsAuthenticationException.<clinit>(BadCredentialsAuthenticationException.java:25)
at
org.jasig.cas.authentication.AuthenticationManagerImpl.authenticate(AuthenticationManagerImpl.java:113)
at
org.jasig.cas.CentralAuthenticationServiceImpl.delegateTicketGrantingTicket(CentralAuthenticationServiceImpl.java:262)
at
org.jasig.cas.web.ServiceValidateController.handleRequestInternal(ServiceValidateController.java:126)
...
...
Which I believe to be an SSL issue,
Can someone confirm if my steps below are accurate?
1.) Configure WebSphere to be secure. Accessing my application and CAS can be
done via https.
2.) View the certificate in a browser and export the certificate as DER encoded.
3.) import the cert into the java keystore used by WebSphere. (This is a
Solaris box).
4.) Bounce WebShpere.
-- Am I missing any steps?
-- Is there more information I should provide to help isolate this issue?
-- Any other debugging tricks that come to mind?
Thanks for all your help!
-Randy
--
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
