Shibboleth Identity Provider 3.2.1 custom authentication configuration

[Raymond Gardner]

>> Yell at the SP? ;-)
>> [Raymond Gardner] I am also the SP.  Yelling at myself will not 
>> impress my boss.

>Then you've created a problem and you can solve it. SPs have no business creating unusual authentication requirements at the IdP. You should start from first principles and rethink what it is you're doing that requires you to force the IdP to do all this.
[Raymond Gardner] You seem to be losing me.  This is not a SP requirement.  All the SP cares about is that the Subject -> NameID is valid as well as any extra attributes.
These are authentication requirements.  The IdP is responsible for authentication.

>> There's simply nothing like this out of the box.
>> [Raymond Gardner] I was thinking I could extend the Transforms bean 
>> and provide a DBTransforms bean.

>It doesn't work like that. The bean is just a regular expression/replacement pair. It's data, not behavior. The behavior is hardwired into a class you can't change.
[Raymond Gardner] I'm just trying to transform the username.  Whether that happens by regular expression or by a mapping stored in a database, it shouldn't matter.
If the application doesn't support this, then the application doesn't support it.  That is fine.

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

****************************************************************
This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. NTT America makes no warranty that this email is error or virus free. Thank you.
****************************************************************