Using Different SecurityPolicy for different SP's?

Zmuda, Matthew R Matthew.R.Zmuda at td.com
Tue Dec 18 10:53:37 EST 2012


Any docs around doing something like this?


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Tuesday, December 18, 2012 10:36 AM
To: Shib Users
Subject: Re: Using Different SecurityPolicy for different SP's?

On 12/18/12 10:24 AM, "Zmuda, Matthew R" <Matthew.R.Zmuda at td.com> wrote:

>Thinking about this a little more and what my options might be.. what 
>if I write a custom Security Rule for the existing Security Policy 
>which has some logic to check the request and only require the request 
>to be signed on non unsolicited SSO requests. That should allow me to 
>use Unsolicited SSO without impacting existing RP config so they would 
>still have send signed requests.
>
>Thoughts on that?

I don't think you have any way to tell that, and regardless you don't have to. As I said, I was wrong, and you can create a dedicated RelyingParty, add the profile handler to that only, and create a custom policy and reference it from there.

-- Scott


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

NOTICE: Confidential message which may be privileged. Unauthorized use/disclosure prohibited. If received in error, please go to www.td.com/legal for instructions.
AVIS : Message confidentiel dont le contenu peut être privilégié. Utilisation/divulgation interdites sans permission. Si reçu par erreur, prière d'aller au www.td.com/francais/avis_juridique pour des instructions.


More information about the users mailing list