<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Raja,<div><br></div><div><div><blockquote type="cite"><div>Actually i'm new to SAML implementation due to that i don't know how to deploy the separate SAML SP's for each sub domain, if you don't mind can you provide little bit more guide on that.</div></blockquote><div><br></div><div>I don't know what else I would say. Each server for each subdomain operates its own SP with unique configuration for that subdomain and its associated IdP.</div><br><blockquote type="cite"><div>I'm totally confused with applicationoverride, please clarify my doubt regarding this.</div><div><br></div><div>1) site name : shall i specify it as <a href="http://xxxx.com/">xxxx.com</a> or <a href="http://sp.xxxx.com/">sp.xxxx.com</a></div>
<div>2) if i specify site name as a <a href="http://sp.xxxx.com/">sp.xxxx.com</a> then is it necessary configure <a href="http://sp.xxxx.com/">sp.xxxx.com</a> in application default section</div><div>3) is there any specific pattern for the host name to use them in the applicationoverride?</div>
<div>4) please classify applicationdefault and applicationoverride based our requirement</div></blockquote><br></div><div>I'd only use it if you need a single SP to protect all the subdomains simultaneously. Hostnames match whatever the clients think they're talking to.</div><div><br></div><div>Hosts and paths are not connected to application ID's automatically. In your environment, you would need to set up mapping from subdomains to ApplicationOverrides. There is an example for how to do that in the article I linked.</div></div><div><br></div><div>Hope this helps,</div><div>Nate.</div></body></html>