<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Alex,
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="">Thanks a lot, I think I'm starting to get a more clear picture of what to do..</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>I think you are, too.</div>
<br class="">
<blockquote type="cite" class="">
<div dir="ltr" class="">
<div class="">No. I would like them to look like one application to the IdP</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>From what I have read, I would want to use one entityID. I would consider that to be an advantage, not a drawback. The two applications become your implementation detail and the IdP knows you as one application.</div>
<div><br class="">
</div>
<div>It's very hard to change this after you go to large-scale production, so make sure to think through all future use cases, too. That might be a reason to avoid this, or a reason it's even better.</div>
<br class="">
<blockquote type="cite" class="">
<div dir="ltr" class="">
<div class="">Yes, this seems to make the most sense. I tried the approach with one entityID and it didn't work because of the attributePrefix conflict. I then attempted the configuration with two entity IDs, which worked successfully, but created the problem described
in my previous post.</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Yep. If you want to do this, you need to:</div>
<div><br class="">
</div>
<div>1) Make the session cookie accessible to both applications</div>
<div>2) Come up with a resolution for the attributePrefix situation.</div>
<br class="">
<blockquote type="cite" class="">
<div dir="ltr" class="">
<div class="">I think what would make the most sense to me is <i class="">setting multiple attributes in the SP from a single SAML attribute with attribute-map.xml</i>.</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>I think that would make sense, too. I don't have any strong feelings about the options I laid out for this.</div>
<br class="">
<blockquote type="cite" class="">
<div dir="ltr" class="">
<div class="">If I can resolve the attributePrefix issue with attribute-map.xml mappings, and both my applications will be covered under one entityID, then will the user only need to authenticate through the IdP once to get access to both applications? </div>
</div>
</blockquote>
<br class="">
</div>
</div>
<div>And you make the cookie in a sub-domain(or domain) that both can see, yes.</div>
<div><br class="">
</div>
<div>Thanks for all the deep thought,</div>
<div>Nate.</div>
</body>
</html>