Hi Robert, Misagh, et. al.,
I think it depends on what you mean by "populate attributes directly."
If your authentication call can store the attributes of interest somewhere
that a personAttributeDao can retrieve them from (a database table, a
distributed cache, etc.), then the dao can make them available to the
attributeRepository. I've done this kind of thing in the past and it's
pretty simple. It's maybe not "populate attributes directly" but it could
save you that second web service call.
Dan
Dan Ellentuck
On Mon, Apr 7, 2014 at 3:14 PM, Misagh Moayyed <[email protected]> wrote:
> I doubt it. You'd have to build one that talks to the WS.
>
> > -----Original Message-----
> > From: Robert Oschwald [mailto:[email protected]]
> > Sent: Monday, April 07, 2014 10:38 AM
> > To: [email protected]
> > Subject: [cas-user] populating attributes from same source as
> authentication
> >
> > I'm wondering if it is possible to populate attributes directly from the
> > authentication source without performing a 2nd call.
> > I already receive the additional attributes from a web service as a
> response
> > to the authentication call.
> >
> > Is there a special attributeRespository available which I can fill
> during
> > authentication?
> >
> >
> > Robert
> >
> >
> >
> >
> > --
> > You are currently subscribed to [email protected] as:
> > [email protected] To unsubscribe, change settings or access archives,
> see
> > http://www.ja-sig.org/wiki/display/JSG/cas-user
>
>
> --
> You are currently subscribed to [email protected] as:
> [email protected]
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
>
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
