[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-users
Subject:    Re: Loading URLTemplate URL from a Separate XML File
From:       Peter Schober <peter.schober () univie ! ac ! at>
Date:       2020-06-24 14:31:20
Message-ID: 20200624143119.wg3ylcqlogpi5c3d () aco ! net
[Download RAW message or body]

* Joshua Brodie <josbrodie@gmail.com> [2020-06-23 20:35]:
> I can do so for XML files - but I wasn't sure if
> '%{idp.attribute.resolver.cdata.url}' can be loaded from XML file,
> and dynamically -- or if there could be other options.

"dynamically" being an additional requirement that's not possible to
satisfy using Java properties (as those are only reliably loaded on
JVM start) -- so far you only mentiond externalising the URL for
deployment purposes:

> As the URL can change -- but don't want to have it in the
> 'attribute-resolver.xml' (to simplify the promotion between
> environments).

How about loading more than just that one string value (the grouper WS
API URL) remotely -- I suppose you can load an extra resolver via
services.xml and then put the whole data connector (and possibly
attribute defs) in there?

Though personally I'd rather handle any such variances/complexity in
deployment/configuration management tools (e.g. Ansible) instead of
expecting all applications to support their own custom method.

-peter
-- 
For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe@shibboleth.net
[prev in list] [next in list] [prev in thread] [next in thread]