<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">Hi,</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;"> </div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">Of course it's only a part of the process.</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;"> </div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">I am migrating an IdP3, and in our running legacy installation we have :</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;"> </div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">attribute-resolver.xml</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">----------------------------</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;"><resolver:AttributeDefinition id="eduPersonTargetedID" <br />xsi:type="ad:SAML2NameID" sourceAttributeID="persistentID" <br />nameIdFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"><br /><resolver:Dependency ref="myStoredId" /><br /><resolver:DisplayName xml:lang="en">Targeted ID</resolver:DisplayName><br /><resolver:DisplayDescription xml:lang="en">Targeted ID: A unique identifier for a person, different for each service provider.</resolver:DisplayDescription><br /><resolver:AttributeEncoder xsi:type="enc:SAML1XMLObject" name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" /><br /><resolver:AttributeEncoder xsi:type="enc:SAML2XMLObject" name="urn:oid:1.3.6.1.4.1.5923.1.1.1.10" friendlyName="eduPersonTargetedID" /><br /></resolver:AttributeDefinition></div>
<div> </div>
<div><!-- StoredID (persistentID) --><br /><resolver:DataConnector id="myStoredId"<br />xsi:type="dc:StoredId"<br />generatedAttributeID="persistentID"<br />sourceAttributeID="eduPersonPrincipalName"<br />salt="%{idp.persistentId.salt}"<br />queryTimeout="0"><br /><resolver:Dependency ref="%{idp.persistentId.sourceAttribute}" /><br /><dc:BeanManagedConnection>shibboleth.MysqlDataSource</dc:BeanManagedConnection></div>
<div> </div>
<div>global.xml</div>
<div>--------------</div>
<div><bean id="shibboleth.MysqlDataSource"<br />class="org.apache.tomcat.dbcp.dbcp2.BasicDataSource"<br />p:driverClassName="com.mysql.jdbc.Driver"<br />p:url="jdbc:mysql://localhost:3306/shibboleth"<br />p:username="shibboleth"<br />p:password=A_TEN_YEARS_OLD_PASSWORD"<br />p:validationQuery="select 1"<br />p:validationQueryTimeout="0" /></div>
<div> </div>
<div>saml-nameid.properties</div>
<div>-------------------------------</div>
<div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">idp.persistentId.sourceAttribute = eduPersonPrincipalName<br />idp.persistentId.salt = A_SALT</div>
<div style="font-family: arial, helvetica,sans-serif; font-size: 10pt; color: #000000;">idp.persistentId.generator = shibboleth.StoredPersistentIdGenerator<br />idp.persistentId.dataSource = shibboleth.MysqlDataSource<br />idp.persistentId.computed = shibboleth.ComputedPersistentIdGenerator</div>
</div>
<div> </div>
<div> </div>
<div>According to what I have read here <a href="https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631673/PersistentNameIDGenerationConfiguration">https://shibboleth.atlassian.net/wiki/spaces/IDP4/pages/1265631673/PersistentNameIDGenerationConfiguration</a> I was thinking another DataSource type could be specified, while also applying the recipe about StoreId removal (after IdP3->4 syntax migration of course).</div>
<div> </div>
<div>But maybe I am mistaking or missing something, it's quite new stuff for me.</div>
<div> </div>
<div>If there is no other convenient option, I wil stick with MySQL (MariaDB this time).</div>
<div> </div>
<div>Regards</div>
<div><br /><br />Le 28-Oct-2022 17:01:49 +0200, rdw@steadingsoftware.com a écrit:</div>
<blockquote style="margin-left: 0; padding-left: 5px; border-left: 2px solid navy;">> According to what I have read here <a href="https://shibboleth.atlassian.net/wiki/spaces/KB/pages/3032940563/Moving+away+from+StoredID" target="_blank" rel="noreferrer noopener">https://shibboleth.atlassian.net/wiki/spaces/KB/pages/3032940563/Moving+away+from+StoredID</a> , I could use an HTTP DataConnector instead of a RelationalDatabase.<br /><br />That’s not how I read that page. It seems to be a recipe to stop using StoredId and rather look up a DB and if there is nothing there just generate a computed ID.<br /><br />> the write operations are defined/configured at the DataConnector level. Maybe there are limitations ?<br /><br />Pretty much by definition Data Connectors are read, not write. <br /><br />/Rod<br /><br /><br />-- <br />For Consortium Member technical support, see <a href="https://shibboleth.atlassian.net/wiki/x/ZYEpPw" target="_blank" rel="noreferrer noopener">https://shibboleth.atlassian.net/wiki/x/ZYEpPw</a><br />To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net" target="_blank" rel="noreferrer noopener">users-unsubscribe@shibboleth.net</a></blockquote>
<br/><hr>FreeMail powered by <a href="https://mail.fr" target="_blank">mail.fr</a>