StoredID setting in Shibboleth v5

[深瀬尚子]

Hi! Rod.

Thank you for your advice.
You're right.

I reconfigured my settings, and I could solve the problems.

I appreciate your suggestion.

________________________________________
差出人: users <users-bounces at shibboleth.net> が Rod Widdowson <rdw at steadingsoftware.com> の代理で送信
送信日時: 2024年3月4日 19:07
宛先: 'Shib Users'
件名: RE: StoredID setting in Shibboleth v5

> As you said, I moved the "MyDataSource" setting to the global.xml and restarted the jetty service.
[....]
> I have the MyDataSource bean setting in the saml-nameid.xml.


> in file [/opt/shibboleth-idp/co
> nf/global.xml]: Could not resolve parent bean definition 'shibboleth.StoredPersistentIdGenerator'

It seems to me that you have " MyPersistentIdStore" in global.xml which is not what I suggested that you do.

I think you need to review your configuration, thinking carefully about what you are trying to achieve.

As a simplification the rules go:

 - Bean definitions in global.xml can only refer to
      1) documented  beans (for global.xml)
      2) other bean definitions in global.xml
 - Bean definitions in subsidiary files (attribute-resolver, saml-nameid) can only refer to
      1) documented beans for global.xml
      2) documented beans for that file
      3) bean definitions in global.xml
      4) bean definitions in that file only.

You CANNOT define a bean in a one subsidiary file and expect to see it in another on.

HINT, in your original mail:

- you refer to MyDataSource in attribute-resolver.xml
   > <BeanManagedConnection>MyDataSource</BeanManagedConnection>

- you refer to MyDataSource in saml-nameid.xml
  >         p:dataSource-ref="MyDataSource"

- you refer to shibboleth.StoredPersistentIdGenerator" saml-nameid.xml



--
For Consortium Member technical support, see https://shibboleth.atlassian.net/wiki/x/ZYEpPw
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net