Migrated from Stored Persistent ID to Computed

[Joshua Brodie]

We have had ongoing performance issues w.r.t Oracle and stored persistentID
-- even with retry below.

In moving from stored to computed  -- are these the following 2 changes to
make?


SAML-NAMEID.PROPERTIES
(the stored ID is the commented out lines)

# Set to an empty property to skip hash-based generation of first stored ID

idp.persistentId.computed =

idp.persistentId.generator = shibboleth.ComputedPersistentIdGenerator

#idp.persistentId.generator = shibboleth.StoredPersistentIdGenerator

#idp.persistentId.dataSource = OracleDataSource

idp.persistentId.sourceAttribute = uid

idp.persistentId.salt = foobar+




ATTRIBUTE-RESOLVER.XML
STORED

<resolver:DataConnector id="myStoredId" xsi:type="dc:StoredId"
generatedAttributeID="persistentID" sourceAttributeID=
"%{idp.persistentId.sourceAttribute}"  queryTimeout="PT5S"transactionRetries
="5" retryableErrors="72000 23000">

<resolver:Dependency ref="%{idp.persistentId.sourceAttribute}" />

<dc:BeanManagedConnection>OracleDataSource</dc:BeanManagedConnection>

    </resolver:DataConnector>

COMPUTED

    <resolver:DataConnector id="myComputedId" xsi:type="dc:ComputedId"
sourceAttributeID="%{idp.persistentId.sourceAttribute}" generatedAttributeID
="persistentID" salt="%{idp.ComputedIDDataConnector.salt}"/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180730/4a781588/attachment.html>