also posted in the "Pac4j users mailing list" group as well.
Hi, I'm hoping my usage is pretty common & someone has already made this
scenario work properly.
My objective is to use the bujio-pac4j-demo-master (3.2.0-SNAPSHOT) project
as a starting point as a CAS client, having CAS delegate via
Setting maxAge=-1 will result in cookie expiry at end of session.
I have this in my config but it may be for 5.1:
# default is P14D
# used to set maxAge on user selection of remember me at login
# it is always set regardless of user choice; this is a bug to investigate
# file:
Thanks Misagh. I was able to acheive things with what you have mentioned.
can you please help me out with statsD thing.
Post:
https://groups.google.com/a/apereo.org/d/msgid/cas-user/c75e153f-8c4d-434e-8bb9-883ca00728f0%40apereo.org
The WARN message that you get is about "*ServiceThemeResolver*", doesn't
means your service is not loaded, just your *theme *not loaded (i.e. you
look is not loaded). The OAuth in general should be working in 5.2.0, since
I am also using OAuth on 5.2.x.
As to how to fix this, 5.3.x will fix
>From your logs:
Preparing to validate ticket [/serviceValidate] for service
[ST-1-Kt3tSwNS7-WALoEctIOCQu1GD68EDWTS017] via
[AbstractWebApplicationService(id=http://localhost:3001/login?destination=%2F,
originalUrl=http://localhost:3001/login?destination=%2F,
Thank's for your answer, I have made a mistake in my report, it's https://
instead of http:// the issue still there.
Regard's
On Mon, Apr 2, 2018 at 4:46 PM, Uxío Prego wrote:
> ... http://localhost:8443/cas/login is a poorly idiomatic configuration,
> hinting... that, or
Hi,
When I examine cookie information after logging in with Remember Me, there
is a TGC cookie with an expiry date 'at end of session'. From my
understanding, it should show the expiry date (1 month from now). Which
implies that my CAS remember me config is not correct.
I am very new to CAS