<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
I'm running v5.1</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
I want to set a different entityID to use during the authn/SAML flow (proxying) because InCommon will not allow a single entityID to be registered as both an IdP and an SP. By default, the IdP software uses the one entityID for both the IdP side and the SP
side. I'd love to be able to set a different entityID to use on the other side of the 'proxy boundary' where the IdP becomes an SP (when using authn/SAML login flow). Unfortunately I dont see a single setting for this.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
I know this is configurable on the relying party via the 'issuer' property and I know if can even provide a issuerLookupStrategy to programmatically set the value. In theory, I should be able to create a relying party override for InCommon entities and it should
get used any time the IdP needs to operate with an entity registered in InCommon.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
The problem is, I dont really know how to figure out if the system is currently operating in SP mode. I think in these cases, a separate ProfileRequestContext is created under the AuthenticationContext and that PRC is what is passed to my strategy. Given
that, I should be able to get the OutboundMessageContext and find its underlying SAMLPeerEntityContext to determine if its entityID matches the default entityID for the system and its "role" corresponds to the SPSSODescriptor. However in my testing, the OutboundMessageContext
never seems to be set up properly. Its "role" is always null and its entityID matches the entityID of the upstream IdP that the user selected. </div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
What am I doing wrong here?</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 11pt; color: rgb(0, 0, 0);" class="elementToProof">
-Bobby Lawrence</div>
</body>
</html>