Disable NameIDGenerator for specificy relyingParty

Ignacio Amoeiro Bosch ignacio.amoeiro at extern.ibsalut.es
Fri May 22 18:57:09 UTC 2020

Ok, now is working.

I didn't understand well how spring framework Works.

So, to clarify my self, 

Has the same effect:

<ref bean="shibboleth.SAML2PersistentGenerator" />


<bean parent="shibboleth.SAML2PersistentGenerator"/>


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

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

> I  swaped, but still not working. It is still triggering the Persistentent generator instead of the AtributeSourcedGenerator.
> This is the list content:

The attribute sourced plugin is now third in your list, after two others. The first one will run using a default computed or stored ID for all RPs other than O365, and the second one will do the same but globally and is being used.

You need move the attribute sourced version running for O365 first and get rid of the other one with the NOT condition since it will never be hit.

-- 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=9c3cf50c-c799-4779-8078-71a3246c01a0&auth=1c980b950b810d2ebe959a136e6fc6796ec23183-52cbdcb3baec1a7b42c5a829c87bab1681a63d3d
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list