We setup our IdP 3 1/2 years ago and haven't gone down the 'store computed IDs' road. My guess is that is that it's just a different piece of work for the IdP to do, but it depends whether querying a database is quicker/less processor intensive.
eLearning Technologist, Hull College Group
Room L34 - Queens Gardens Library
Wilberforce Drive, Queen's Gardens, Hull, HU1 3DG
Extension 2230 / Direct Dial 01482 381930
From: Discussion list for Shibboleth developments [[log in to unmask]] on behalf of John Horne [[log in to unmask]]
Sent: 21 February 2014 12:01
To: [log in to unmask]
Subject: Calculating attributes on the fly or use local DB?
I am new to using Shibboleth IdP (2.4), but we are setting up two new
servers for our site. Most of the work has already been done (mostly by
contractors, a little tweaking by us).
We have an attribute (eduPersonTargetedID/persistentID) which requires a
calculated value similar to the 'computedID' attribute. Currently this
value is calculated when first required, but then stored in a local
MySQL database. On subsequent requests for the attribute, the MySQL
database is used to look up the value (or so I gather. I've still to
work out how shibboleth actually stores and retrieves the value).
My question though is, is it worth using a DB to store/lookup the value?
Is there any advantage in using a local DB? Would it not be a simper
configuration to just calculate the attribute value on the fly (the same
as 'computedID')? This also then avoids us having to maintain the DB
(removing old records etc etc).
John Horne Tel: +44 (0)1752 587287
Plymouth University, UK Fax: +44 (0)1752 587001