I'm trying to use the Login Redirect URL option a contract, however I can't see that this triggers identity injection against the backend web server (configured as a protected resource).
I do get redirected to the specified URL, but not auto-logged in there (based on the auth header from II).

From NAM's perspective, we're in a halfway authenticated scenario (authenticated, but not yet at destination resource, taking a detour via a LoginRedirectURL).

Am I incorrect in expecting that all the standard NAM stuff like form fill and II works at this point?