Re: Setting up multiple SPs with one single IDP

Thanks David.
That really helped. I was able to finally setup two SPs and one IDP. I
added links to the sample home.aspx page to link to the SPs from each
other. When I tested single sign-on, it worked.
By the way, I'd be glad send you the sample projects I created along with
their web configuration files if you think other users might benefit from
it. I also have a database script that creates the account_federations
table with the right indexes/primary keys. I think a test with two sites
illustrates the single signon idea better.

I have a few  other questions related to authentication on other pages
besides the home.aspx page, and integration with other types of web apps.
a) Do you have to always check for the Session["sso-sample.userID"] and
make sure it's not null(see code snippet below) to allow a user on the
page, or is there another mechanism I am not aware of?
b)How do you integrate the SourceID single signon feature with a plain ASP
web app?
c)How do you integrate the SourceID single signon feature with a cold
fusion web app? (I suspect this to be similar to ASP. I am not a cold
fusion personally, but I am sure it provides a session object similar to
ASP, and thus the solution is likely to be the same as b.)

Thanks,
Mamoud.

Code Snippet from Home.aspx
 UserID = (string) Session["sso-sample.userID"];
            if (UserID == null)
            {
                UserID = (string) Context.Items[Constants.Context.UserId];
                if (UserID != null)
                {
                    Session["sso-sample.userID"] = UserID;
                }
            }
            if (UserID == null)
            {
                Server.Transfer("logon.aspx", true);
                return;
            }