a use case single domain

[Peter Schober]

* Ci98yr <ci_98yr at yahoo.com> [2013-01-18 11:25]:
> would like to gain some insights into applying for two different
> systems but belonging to the same domain

By definition if you can make it work across DNS domain borders it
will also work within a single DNS domain. Just as well.

> a) would this be a good solution at all based on saml

Certainly. Shibboleth gives you a lot of power and flexibility and
you'll probably soon conclude that "internal" and "external" are not
really useful categories to seperate services, policy-wise.
E.g. not all "internal" services might be equally trustworthy and some
critical business systems might be hosted externally.
By using Shibboleth and SAML for both classes that issue is being
transformed into concrete policy decisions regarding attribute
release, session length, authentication method, etc.

> b) where does user id mapping logic resides (need to be developed separately ?) 

I don't understand the question and it also does not seem to be a
function of whether SSO happens across or within DNS domains.
-peter