SP v4 alpha2 and discoveryURL ?

[Scott Cantor]

I'll test further "in anger" with an actual discovery scenario, but in my unit testing, issuer is getting pulled in as expected.

If I set sp.issuer, define p:issuer in an Agent, then define an Application with no p:issuer, my test sees the Agent bean's p:issuer value, not the sp.issuer property.

The discovery code is pulling it in a way that should come from that source, so I can't reproduce it artificially, I'll see what happens when I can test it more realistically.

What is a problem that I do know about is things go sideways when you make it even worse and start doing RelyingParty Overrides. You didn't show that, but if you're doing that, it in fact ends up reverting to the sp.issuer property value there.

That's known, and I think I even documented it, but it's such a convoluted mess it wouldn't be obvious.

The problem is that I don't have any viable way to implement inheritance across the RelyingParty objects; the IdP doesn't work that way and this is using that code, so it works the way the IdP did and everything "resets" back to a default set of settings when RP overrides get used.

I don't like it, and I especially hate it with "issuer" but it does do that at the moment, and that's a much bigger problem here than in the IdP where entityID doesn't tend to vary as much across the configuration.

Anyway, could be that.

-- Scott