ORA-08177: can't serialize access for this transaction

[Lionel Samuel]

We have a myriad of vendors ---- some  accept nameIDs, a minority are still
only eduPersonTargetedID ......it wasn't by choice, but keeping the ship
running..

Beyond unelegance, does it create any unorthodox behaviors on the IdP or
future upgrade path.

On Mon, Sep 11, 2017 at 1:43 AM, Peter Schober <peter.schober at univie.ac.at>
wrote:

> * Lionel Samuel <lionel.samuel01 at gmail.com> [2017-09-11 06:22]:
> > We are recently on idp3.3.0 and enabled:
>
> Also want to share why you're creating NameIDs in the attribute
> resolver? Any application that requires eduPersonTargetedID to work
> but can't use (the same) persistent NameIDs when sent in the
> Assertion's Subject element should be fixed (and have a bug reported).
> -peter
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170911/a2b4846c/attachment.html>