[cas-user] CAS 6.x delegated auth chanied with different attributeRepository

2019-04-12 Thread Julien Gribonvald 

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/b10edc58-e9cf-b4d9-e0d7-400c122da3da%40recia.fr.

Re: [cas-user] CAS 6.x delegated auth chanied with different attributeRepository

2019-04-16 Thread Julien Gribonvald 

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/046352a4-29f0-f3a3-c4e8-6b05a233cef0%40recia.fr.

Re: [cas-user] CAS 6.x delegated auth chanied with different attributeRepository

2019-04-26 Thread Misagh Moayyed 
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.

Re: [cas-user] CAS 6.x delegated auth chanied with different attributeRepository

2019-04-29 Thread Julien Gribonvald 

Thanks Misagh,

Ok, so don't hesitate to notify me when the feature will be available.

Julien

Le 26/04/2019 à 20:36, Misagh Moayyed a écrit :
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 
.

--
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/6e7e710e-7bbc-f3e3-9db5-932605cadf1d%40recia.fr.