RE: [saml-dev] URLs

[Matt Kendall <Matt.Kendall@epeople.com>]

It will be very difficult for ePeople to conform to the host naming
proposed.  Our application is a multi-tenant hosted application and the
first part of the hostname has special significance - it is the switch used
to switch between installations of our product.  It would be much easier for
us to use the same hostname for both "application" and "receiver".

Matt Kendall
Director of Engineering
ePeople
matt@epeople.com
http://www.epeople.com


  
-----Original Message-----
From: Philpott, Robert [mailto:rphilpott@rsasecurity.com]
Sent: Wednesday, June 12, 2002 11:49 AM
To: 'Tahura Chaudhry'; saml-dev@lists.oasis-open.org
Cc: Irving Reid
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
mailto:rphilpott@rsasecurity.com

-----Original Message-----
From: Tahura Chaudhry [mailto:Tahura.Chaudhry@baltimore.com] 
Sent: Wednesday, June 12, 2002 2:17 PM
To: saml-dev@lists.oasis-open.org
Cc: Tahura Chaudhry; Irving Reid
Subject: [saml-dev] URLs

Here are Baltimore's URLs:

Inter-site     : https://samltest.baltimore.com:9985/saml_out/
Receiver     : https://samltest.baltimore.com:9985/saml_in/
Responder  : https://samltest.baltimore.com:9984/saml_responder/  

For now, both our portal site URL and our application URL will be the same.
This will probably change later.
http://samltest.baltimore.com/SAMLDemo/index.asp

SourceID     : 1ea6b9afbc7e9fa72b95f73362624fe13da6be65
Issuer         :  www.baltimore.com
Certificates : TBD

thanks,
Tahura



----------------------------------------------------------------------------
-------------------------------------
The information contained in this message is confidential and is intended
for the addressee(s) only. If you have received this message in error or
there are any problems please notify the originator immediately. The 
unauthorised use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for
direct, special, indirect or consequential damages arising from alteration
of the
contents of this message by a third party or as a result of any virus being 
passed on.

This footnote confirms that this email message has been swept for Content
Security threats, including
computer viruses.

http://www.baltimore.com


This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.