<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<pre wrap=""><i>In fact, ComputedID is henceforth depreciated for that reason we use
PersistentID with StoredID connector which generate random identifiers and
store them in db.
</i></pre>
<i> </i></blockquote>
<i> </i>
<pre wrap=""><i>"Computing them hasn't been deprecated in any real way for a very long time. It's the only practical way to do them, a database is not a practical approach for the vast majority of deployers."</i>
</pre>
Sorry about it and thank you for providing this information.<br>
I've shared the information received from our Federation last year
that's why we had to change our configuration to use Stored ID in
IdP2.<br>
I've just checked from their site the Compted ID is still announced
like obsolete and it is strongly advised not to use it.<br>
However, for IdP3, both of them are proposed and StoredID is
recommended.<br>
<br>
I think, there was a confusion about it.<br>
I'll report them.<br>
<br>
Another point : delegate the authentication IdP3 to CAS <br>
Our principal SSO solution is CAS (v3.5.2)<br>
Would it be a good idea to integrate an external CAS server with
IdP3 ?<br>
What do you think about this approach ?<br>
<br>
Visibly, it's possible with Unicon projet :<br>
<a class="moz-txt-link-freetext" href="https://github.com/Unicon/shib-cas-authn3">https://github.com/Unicon/shib-cas-authn3</a><br>
<pre class="moz-signature" cols="72">Marc SAHIN
Administrateur Systèmes
Pôle Système - DSI - Université Lumière Lyon 2
04 78 77 26 66
</pre>
<div class="moz-cite-prefix">On 01/12/2016 17:15, Cantor, Scott
wrote:<br>
</div>
<blockquote
cite="mid:9846A6064BD102419D06814DD0D78DE112AC13CC@CIO-TNC-D2MBX02.osuad.osu.edu"
type="cite">
<blockquote type="cite">
<pre wrap="">In fact, ComputedID is henceforth depreciated for that reason we use
PersistentID with StoredID connector which generate random identifiers and
store them in db.
</pre>
</blockquote>
<pre wrap="">Computing them hasn't been deprecated in any real way for a very long time. It's the only practical way to do them, a database is not a practical approach for the vast majority of deployers.
</pre>
<blockquote type="cite">
<pre wrap="">It's easy to put in place dynamic PersistentID but it has some limitations ; it is
not to possible to find a user with his PersistentID, revoke or modify the
value of the PersistentID...
</pre>
</blockquote>
<pre wrap="">The former is possible with audit logging. The latter isn't possible, but if it ever came up, building a mechanism based on a sparse override file to force changes to the hashes would be well within any mildly competent Java developer's capability.
-- Scott
</pre>
</blockquote>
<br>
</body>
</html>