Disable NameIDGenerator for specificy relyingParty

[Ignacio Amoeiro Bosch]

Ok, thanks for the explanation.

Yes, I knew that spring XML documentation is important to understand shibboleth configuration.

Thanks again for all

-----Mensaje original-----
De: users <users-bounces at shibboleth.net> En nombre de Cantor, Scott
Enviado el: viernes, 22 de mayo de 2020 21:08
Para: Shib Users <users at shibboleth.net>
Asunto: Re: Disable NameIDGenerator for specificy relyingParty

On 5/22/20, 2:57 PM, "users on behalf of Ignacio Amoeiro Bosch" <users-bounces at shibboleth.net on behalf of ignacio.amoeiro at extern.ibsalut.es> wrote:

> I didn't understand well how spring framework Works.

That's why the IdP documentation starts by pointing to the Spring XML docs.

> So, to clarify my self, 
> Has the same effect:
> <ref bean="shibboleth.SAML2PersistentGenerator" />
> than:
> <bean parent="shibboleth.SAML2PersistentGenerator"/>

Functionally, but the former uses an existing object and the latter creates a new one based on the bean definition of the parent. In this particular case that means one extra object created, relatively insignificant. In other cases it could be a major difference.

-- Scott


-- 
For Consortium Member technical support, see https://ddec1-0-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwiki.shibboleth.net%2fconfluence%2fx%2fcoFAAg&umid=5fd8e05f-3f1a-4c2c-8811-3de4aa7f46c0&auth=1c980b950b810d2ebe959a136e6fc6796ec23183-aacf235d17dc9797a374bef0caee5ae5dbc573bf
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net