This isn't quite possible to do as you describe it today. I'd suggest you wait until 6.1 RC4 as this is being somewhat worked. Otherwise, you might need to write your authentication handler and in there decide how to fetch attributes based on the client, etc.
On Tuesday, April 16, 2019 at 2:33:04 AM UTC-7, Julien Gribonvald wrote: > > Hi, > > Sorry to re-run the question but how can I do that ? I've found how to > define a policy with authenticationHandlers but it doesn't help to chain > with an attributeRepository. > > Is it possible to do what I want or I should chain all delegated > authenticationHandlers with all attributeResolver ? > > Thanks, > > Julien > > > Le 12/04/2019 à 11:24, Julien Gribonvald a écrit : > > Hi, > > > > Is there something already existing to map to a specific authn > > configuration a specific authn.attributeRepository ? > > > > I have several kind of external auth system and so the attribute > > resolution locally (local LDAP) should be done by different LDAP > > search request (and so attributeRepository), each authn system should > > have his own attributeRepository, and I need to avoid to chain all > > attributeRepository. Is it possible or should I implement something ? > > > > If I should implement something could you tell me what is the best way > > (and where to look) ? > > > > I'm following the CAS master branch. > > > > Thanks, > > > -- > Julien Gribonvald > -- - 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 Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/1c38d176-bd4f-4fbc-80dd-12c33924df04%40apereo.org.
