Thanks for the hint & instant responses Ray.
Regards
Ramakrishna G
+91 8792114542
On Sat, Aug 4, 2018 at 1:07 AM, Ray Bon wrote:
> Ramakrishna,
>
> This is what I set on my test machine:
>
> upstream casssl {
> server localhost:8491;
> server localhost:8492
Ramakrishna,
This is what I set on my test machine:
upstream casssl {
server localhost:8491;
server localhost:8492 backup;
}
location /cas {
proxy_pass https://casssl;
}
The backup means that all requests go through 8491
Do you mean to say ip-hash as load balancing mechnaism. I have tried that
as well. But No Luck
Thanks
Ramakrishna G
On Sat, Aug 4, 2018 at 12:37 AM, Ramakrishna G wrote:
> Ray,
>
> Can you please elaborate this "If you set nginx to be sticky, will
> validation succeed?" Any example for this.
>
Ray,
Can you please elaborate this "If you set nginx to be sticky, will
validation succeed?" Any example for this.
Also in cas logs I could see ticket was not validated when I go through
NGINX
Thanks
Ramakrishna G
On Fri, Aug 3, 2018 at 11:02 PM, Ray Bon wrote:
> Ramakrishna,
>
> This
Ramakrishna,
This sounds like slow ticket replication. Does redis sentinel have multiple
stores?
If you set nginx to be sticky, will validation succeed?
Check your cas logs to see if the ticket is being validated. I think the cas
client tries to validate the ticket using https.
You could
Hello all,
I am using Mod_auth_cas and HA- Cas server behind a loadbalancer.
Whenever I set CASValidateURL to one of the cas servers it works fine. But
when I send to cas via NGINX server then it says "Unauthorized error" in
browser.
My Nginx has
location /cas/login
{
proxy_pass
