PR is made: https://github.com/apereo/cas/pull/4404 -Andy
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the
Sure. The documentation needs to be complemented here...
Le lun. 4 nov. 2019 à 08:24, Andy Ng a écrit :
> Hi Jérôme
>
> Oh nice, thanks for your explanation :)
>
> I think we should document that *requirement on attribute* on
>
Hi Jérôme
Oh nice, thanks for your explanation :)
I think we should document that *requirement on attribute* on
https://apereo.github.io/cas/6.1.x/installation/MongoDb-Authentication.html
Since the authentication experience is differs from other
Authentication authenticationMethod, (e.g.
Hi,
Yes, this is the expected behavior in pac4j. There are two modes (
http://www.pac4j.org/docs/authenticators/mongodb.html): either you define
the attributes and they are used for the profile OR you don't and a
serializedprofile attribute is expected to store the whole serialized
profile.
In
Hi all,
Today I am testing out CAS using MongoDB authentication, and found out a
behavior for MongoDB Authentication:
> if no attribute was given in cas.authn.mongo.attributes, the
authentication will failed by No serialized profile found.
Here an example:
cas.yml:
cas.authn.mongo:
