This issue has been resolved. I was not importing the certificate to jvm considering that trusted certificates are automatically detected by the Weblogic. While using wild card certificate all the products and CAS server used the same certificate so there was no problem. In the later case, CAS server's certificate has different certificate. Now I imported CAS server's certificate in all the products JVM and the issue is resolved.
Thanks and Regards,
Lekhnath

Andrew Feller wrote:
Lekhnath,

Could you post a description of the error?  Where does it occur?  Service
ticket validation?

Friendly note: [email protected] is for the development of the CAS
project while [EMAIL PROTECTED] is for user support in deploying and
troubleshooting issues like this.

Thanks,
A-

On 12/9/08 4:34 AM, "Lekhnath Bhusal" <[EMAIL PROTECTED]> wrote:

  
Hello team,
I have four products configured to authenticate through a single CAS
server. My issue is:
I used a domain certificate (from sitesafe network solutions) like
*.mydomain.com in all the products and CAS server. I disabled host name
verification in all application servers. In this context it works fine.
Now due to some third party application requirements I have to change
that to a different configuration where: CAS server uses
cas_domain.mydomain.com and the rest of the products use *.myDomain.com.
In this configuration SSL verification error occurs. I am using weblogic
10.3 for one product and CAS server deployment and weblogic 8.2 for the
rest of the products. Do I have to make some modifications in the CAS
server or client to accept the fully qualified certificate? Why the
domain certificate is working fine?
This error has compelled me dropping the third party implementation and
revert back to domain certificate in all the products and CAS server.
Please suggest me the solution.
Regards,
Lekhnath


 
PRIVACY NOTICE

This email and any attachments may be confidential and/or privileged. Use of
the information contained in this email by anyone other than the intended
recipient is strictly prohibited. If you have received this email in error,
please notify the sender by replying to this message and delete this email.
_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev
    

_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev


  
_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev

Reply via email to