shibboleth 1.3 AttributeStatement missing when SubjectLocality.IpAddress is external (off campus IP)

[Michael Basil]

I believe the admin and I have this working now.  The external traffic was
going to a different server than the internal traffic (based on the load
balancer algorithm).

We have replicated the forceAttributePush parameter to the config file.  I
will re-test after the service restarts.

Thanks again.

Mike Basil
312.961.7798

On Mon, Apr 2, 2012 at 21:09, Michael Basil <m-basil at northwestern.edu>wrote:

>  Scott,
>
>  My take away from this is that this setup *should* work ... I'll work
> with the admin to see what is causing the issue.
>
>  My understanding is that the NU admin has this setup working with other
> SPs.
>
>  Thanks.
>
>
> Mike Basil
> 312.961.7798
>
>
>
>
> On Mon, Apr 2, 2012 at 15:48, Cantor, Scott <cantor.2 at osu.edu> wrote:
>
>> > We are using browser post.  The URL that is generating the SAML 1
>> request
>> > looks identical minus a state ID (noted below) ... so I don't think it
>> is a
>> > corrupted request.  The request lengths are less than 600 characters
>> too, so
>> > there isn't anything like that in play.
>>
>>  Doesn't seem to be.
>>
>> > Plus, the assertion states the Audience correctly in both cases.
>>
>>  No chance of this happening then, so...no idea. Time to start tracing
>> code and logs.
>>
>> > Could there be Attribute Release Policies in play (that I should have
>> the
>> > admin check)?
>>
>>  No, policies in 1.3 know nothing about the location of the client.
>>
>> -- Scott
>>
>> --
>> 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/20120403/f8329548/attachment.html