...
I can see only some hints in forums but no organized document or
procedure...
Thanks,
Barc
On Sat, May 23, 2015 at 10:22 AM, Ori Raz wrote:
> Thank you Christopher.
> Appreciate all your help. Please let me know if any additional info is
> required for the issue.
> Regar
, both are not working.
Thanks,
Barc
On Fri, May 22, 2015 at 7:13 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ori,
>
> On 5/22/15 10:03 AM, Ori Raz wrote:
> > Thank you Christopher for your
shake failure:s23_clnt.c:583:
Thanks,
Barc
On Fri, May 22, 2015 at 3:17 PM, Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Ori,
>
> On 5/22/15 8:18 AM, Ori Raz wrote:
> > We got an application based on
Hello David,
Thanks for replying.
https://10.56.57.65:8443/
This is the same url that we used before applying our certification.
Thanks,
Barc
On Fri, May 22, 2015 at 2:41 PM, David kerber wrote:
> On 5/22/2015 8:18 AM, Ori Raz wrote:
>
>> Hello experts,
>>
>> We got
Hello experts,
We got an application based on tomcat 7.0.23 and all working fine.
We are trying to apply our self-signed certificate and encountering some
problems.
I hope that the procedure I did is correct :)
This is the procedure we followed:
1. copy the certificate file under this locatio
tomcat and still support old clients?
Thanks,
Ori Fine
everything works as
expected.
Any ideas on what could have changed? My application uses Commons Logging
(required by Struts), Log4J, and Xerces so those jars are being added in the
manner described above. Maybe there is a conflict there?
Thanks,
Ori
-
Full exce
