Ka Lam,
It is not releated with CAS. It is due your instance is unable to
verify certificate to "https://MYCOMPNAME:12345";. Due it supplier
isn't found in truststore. My assumption is that certificate expired,
and administrators added new certificate for MYCOMPNAME:12345.
Hope this will help you understand this issue and avoid it next year.
Best regards,
Augustyn.

On 28 May 2014 at 12:35, Ka Lam <kalam.c...@znap.com> wrote:
> Things looks ok after i restart the servers....sorry for my carelessness!
> --
> You are currently subscribed to cas-dev@lists.jasig.org as: 
> augustynw...@gmail.com
> To unsubscribe, change settings or access archives, see 
> http://www.ja-sig.org/wiki/display/JSG/cas-dev

-- 
You are currently subscribed to cas-dev@lists.jasig.org as: 
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-dev

Reply via email to