Profile Configuration parsing
Cantor, Scott
cantor.2 at osu.edu
Wed Mar 5 11:35:19 EST 2014
On 3/5/14, 11:02 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>a) I am not even considering anything in the Security schema for now. We
>may decide to jettison it in its entirety, or we may not. For now the
>uses
>that that ProfileConfiguration and RelyingParty schemas have are by
>reference so our options are open to do pretty much anything.
As I said when we spoke, it seems to me that if we really want to factor
out and share those beans, using an actual service interface we define
that can lookup credentials, trust engines, etc. is the way to go vs.
hacking something based on Spring inheritance.
>b) Equally I do not think that now is the time to make the call on how to
>handle the extra configuration that V3 brings. We may do the embedded
>beans
>thing, or references, or something else. I propose that we wait until
>Daniel reports back on how he gets on with the DataConnectors before we
>discuss and decide this.
+1
>c) Meantime there are a few places where I hard- or soft- wire things up.
>The most notable case was for the ArtifactConfiguration (URL and index).
>These were AFAICS, taken from the Metadata in V2 and this is not an option
>for V3. For now I am just planting a reference to beans whose name is
>derived from the precise configuration (for instance "
>shibboleth.SAML2.Artifact.ServiceURL. Other missing parameterizations
>(e.g. encryptAttributeValues) just grab the defaults.
That's fine. I haven't looked into the way to specify that yet, but I
suspect it will need to be something global to the IdP instance on a
machine. But very likely set via a property anyway. Probably we'd have
every node contain beans defining the URL and index for every node member,
and then select the one to use on a given host with a property. Likely set
via environment or something.
>3) There is a mismatch in the comments the "Audience" elements of
>SAMLPropertyConfiguration which states "List of audiences for issued
>assertions." And the List<String> assertionAudiences field in
>AbstractSAMLProfileConfiguration which has the java doc "Additional
>audiences to which an assertion may be released". I'm pretty sure that
>these are the same thing, but I wanted to check.
Yes, it's the same, you can correct the schema comment if you want.
-- Scott
More information about the dev
mailing list