AACLI to web interface?

[Cantor, Scott]

On 7/21/14, 12:30 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>I think that this might be a good idea but I had one concern which is that
>people would probably not want to make changes to their live setup while
>they were testing.

While I don't care all that much for somebody trying to do it, one could
create a second AttributeResolverService and point the admin tool at it,
and use a copy of those Spring resources, and then stage changes that way.
Essentially an internal dev to production copy cycle.

>Right now, if you are not running a reloadable attribute resolver and
>filter
>you can make changes to your production config and "just" run accli.

I can't, because I have container managed data sources.

>When it the configuration works the way you want you can fire off a
>container.  I
>assume that people with reloadable configs have a sandbox web server that
>they test in.

Yes, but I don't really know what to say to somebody running any IdP
without a dev instance. On the same box if nothing else.

>Once we understand this, is it worth taking it over to -users?

I'm not really keen on copying V3 issues over to users.

-- Scott