possible issue with CDS 1.2.0?

[Cantor, Scott]

On 3/22/12 12:14 AM, "Caskey, Paul" <pcaskey at utsystem.edu> wrote:
>Any idea what could be causing this?  It¹s not all SPs, but for those
>affected, removing the node running 1.2.0 from the cluster fixes the
>problem (other node is running 1.1.3).  I know that one of the affected
>SPs has 3 different URLs and each URL has a corresponding
>DiscoveryResponse element in the metadata.  Might that have something to
>do with it?

It really depends on how relayState is being handled. If by cookie, then
it's possible that there's a vhost issue involved, but I think it's more
likely another regression in 1.2 that broke something about the target
parameter behavior.

-- Scott