Some SAML 1 flow questions

[Cantor, Scott]

On 2/4/14, 12:34 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>> V2 dropped the single assertion option, and I'm not aware that it ever
>> issues two. If it does that for SAML 1 artifact, I didn't spot it, but
>> I'll check.
>
>Certainly at one stage I was seeing three round trips for SAML1
>(login/fetch
>AuthN/fetchAttributes) and the time taken to run a quick test makes me
>feel
>that that it is still like that.  Whether that *matters* is another thing
>entirely.  Noone (except me) has complained.....

Ah, ok, my bad. So you're referring to setting includeAttributeStatement
false, but then doing artifact. Ok, I see it. I think the answer is "we
don't honor include = false if the outbound is artifact".

-- Scott