Hi Bill,
Seems like the CAS team will be fixing this in latest CAS version, see this
commit:
https://github.com/apereo/cas/commit/e214dba59c2273409c406cf4301e2dc875183295
Looks to me they implemented a check this line here:
For UI, you can always consult the official document:
https://apereo.github.io/cas/6.0.x/ux/User-Interface-Customization-Views.html -
Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions:
Hi Vikash,
Would be awesome if you can provide as much information (e.g. CAS version,
which UI element want to chagne, etc...) as possible, so people in the
community can try and figure out the problem.
First of all:
*> Moreover I have added properties for pm: *
Is the LDAP part is already
Hi, I would like to implement simple MFA with my CAS server and send code
via the Signal messenger app. To achieve this I've installed this service
https://morph027.gitlab.io/signal-web-gateway on my server that accepts
requests like these:
curl -X POST -F "to=" -F "message=Test" http:
Hello All,
Please can someone help me. I ma trying to move from our current
shibboleth IDP to CAS, all seems OK but when I start setting up the
registered service it goes wrong. I either get too much information (but
not the info needed) or I don't get any.
I would like to show :
That is good to hear. Thanks for letting me know.
On Wed, Jan 22, 2020 at 9:29 AM Josh wrote:
> Hi Chris -
>
> No luck finding a solution on the error, however the good news is other
> than polluting our logs (which we could mitigate) there does not appear to
> be any negative user impact.
>
>
Hi Chris -
No luck finding a solution on the error, however the good news is other
than polluting our logs (which we could mitigate) there does not appear to
be any negative user impact.
We're several million authentications into this upgrade without any users
reporting issues.
On
Hello Josh,
I have just upgraded from 5.2.X to 5.3.X and am experiencing the same error
and like you, everything seems to be working fine.
Were you able to find a solution to fixing this error?
Thanks!
Chris
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom:
It doesn't make sense for me, see Andy's answer above.
On Wednesday, January 22, 2020 at 4:05:10 PM UTC+2, Roger Yerbanga wrote:
>
> So change it to false and let us know if it works.
>
> On Wed, Jan 22, 2020 at 5:38 AM 'Maksim Kopeyka' via CAS Community <
> cas-...@apereo.org > wrote:
>
>> Same
So change it to false and let us know if it works.
On Wed, Jan 22, 2020 at 5:38 AM 'Maksim Kopeyka' via CAS Community <
cas-user@apereo.org> wrote:
> Same problem with CAS 6.0.3 and JPA ticket registry.
> And yes, I have this
> property: cas.authn.samlIdp.attributeQueryProfileEnabled=true
>
> On
Same problem with CAS 6.0.3 and JPA ticket registry.
And yes, I have this
property: cas.authn.samlIdp.attributeQueryProfileEnabled=true
On Friday, October 19, 2018 at 11:58:55 PM UTC+3, Roger Yerbanga wrote:
>
> Hello all,
>
> With Cas 5.3.4.
>
> Has someone already gotten something like this :
11 matches
Mail list logo
