Context navigation in the Abstract Profile Actions.

[Rod Widdowson]

Thanks.

> That's what I do. I try to push as much error checking into the preExecute
> hook as possible, so there's little or no null checking in the execute
> step.

My instinct is that I will need null checking in the action because AIUI it
can be quite valid to do an attribute resolution without a principal.  It
seems less likely, but is probably still feasible, to not have a requesterID
as well.
 
> The issuer ID doesn't get used
> much if at all, but it will come from
> RelyingPartyContext.getRelyingPartyConfig() I think.
> 
> The method is TBD and I would really rather we consider breaking that one
> thing. Nobody uses it to my knowledge, and it is no longer a well-defined
> concept in the new design.

I'd be happy to break it, I would be very surprised that [m]any have
deployed Shib2 IdPs with multiple entityIDs.

Although this feels slightly strange I think my suggestion on how to achieve
this would be to actually leave everything in place except the actual
population, but also issue an error message during configuration.  Then we
can remove everything at our leisure on a subsequent release, but if someone
does complain loudly enough it is just one bean to modify and slot in.