[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [saml-dev] URLs
Hmmm... I thought we agreed that the URLs would be as declared as in the Interop Scenario document published by Prateek. That is, "application.<dns_suffix>", "portal.<dns_suffix>", etc. This was being done to help with consistency and avoid configuration mistakes.
I suppose it's not really a big deal, since most of us are at least specifying ports and some are also specifying paths on the URL's, so we already have opportunities for mistakes. The consistency made a little more sense in the original definitions that did not include ports and paths. I still would prefer the "agree-to" names.
I just figured I'd point out the deviation and make sure no one has an issue with it and is prepared to handle it.
FYI - For those not familiar with DNS, we are handling the names through DNS "aliases". Thus, using "portal.baltimore.com" and "receiver.baltimore.com" doesn't mean you have separate systems named "portal" and "receiver". We create a DNS host record for the actual system (e.g. samltest.baltimore.com) and just point the alias records to that system. Thus http://portal.baltimore.com/SAMLDemo/index.asp gets sent to samltest.baltimore.com.
Rob Philpott RSA Security Inc. The Most Trusted Name in e-Security Tel: 781-515-7115 Mobile: 617-510-0893 Fax: 781-515-7020
-----Original Message-----
Here are Baltimore's URLs:
Inter-site : https://samltest.baltimore.com:9985/saml_out/ Receiver : https://samltest.baltimore.com:9985/saml_in/
For now, both our portal site URL and our application URL will be the same. This will probably change later.
SourceID : 1ea6b9afbc7e9fa72b95f73362624fe13da6be65 Issuer : www.baltimore.com Certificates : TBD
thanks, Tahura
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC