LDAP Authentication and LDAP Attributes

[Cantor, Scott]

On 10/6/14, 10:37 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>> To be clear, I'm also against the attribute resolver properties being in
>> there.
>
>Absolutely.
> 
>> The difference to me is between configuring the IdP itself, and the
>> settings involved with site-specific integration choices.
>
>I hear you.  So pulling this in another direction, is there mileage in
>adding other integration specific properties files?  My instinct is 'no',
>LDAP is really only of interest (to me) because the same connection is
>(potentially) used at two integration points AuthN and Attributes.

JDBC potentially. Overall it depends how many settings are involved.

>Some sort of
>
>Idp.ldap.properties="whatever"
>
>Or better 
>
>Idp.inetgration.properties="whatever"
>
>?

No, idp.additionalProprties = ldap.properties, jdbc.properties, etc.

A pointer to the additional files to load. That will also let us factor
out other sets of properties if we want to. I'm coding this right now, it
should't take long. We're just loading all of the properties into Spring
now, so we can add additional resources easily enough.

>But in fact my concern is more fundamental, whether spring easily allows
>for
>the configuration of two properties files for property replacement (we
>will
>need both)?

Spring does, but we're subverting that already by manually loading them up
front and not loading them by location in each context, so we just have to
extend the context initializer code to do this.

-- Scott