activactionCondition question

Greg Kuchyt gkuchyt at uvm.edu
Fri Sep 23 08:17:17 EDT 2016


Ok thanks. I misunderstood the docs as I read them. This clears up some of the confusion I was having with this.

On 9/22/16, 09:41 , "users on behalf of Cantor, Scott" <users-bounces at shibboleth.net on behalf of cantor.2 at osu.edu> wrote:

    On 9/22/16, 9:24 AM, "users on behalf of Greg Kuchyt" <users-bounces at shibboleth.net on behalf of gkuchyt at uvm.edu> wrote:
    
    >    If one needs to release an attribute in a different form to a select group of SPs what
    > is the intended way to accomplish this? Example: A couple SPs want uid as username at realm
    
    If you mean provide different data to different SPs while naming it the same thing, there is no intended way, and I would never do it. If they want different data, they get a different attribute, very simple.
    
    > Would you define the attribute twice in attribute-resolver.xml and have one
    > activationCondition for the group of SPs that need the different attribute form or would
    > you define two activationConditions with the second being a negation of the first which is
    > attached that to the "normal" definition of the attribute?
    
    Were I to do something that I would not in fact do, I would attach conditions to the encoders, not the attribute definitions, but it would ultimately depend on the conditions, how efficient they were to express and to run, and the overall impact on the efficiency of the operations.
    
    -- Scott
    
    
    -- 
    To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
    



More information about the users mailing list