>>1. http://portal.<dns_suffix>
>>2. https://inter-site-transfer.<dns_suffix>
>>3. https://receiver.<dns_suffix>
>>4. https://responder.<dns_suffix>
>>5. http://application.<dns_suffix>/application
I forgot to mention this when I brought up port numbers. Our
inter-site-transfer, receiver, and responder URLs have a path component,
because they're all actually served by the same HTTP/SOAP server process. In
a normal SelectAccess configuration, URLs 2, 3, and 4 look like:
Inter-site transfer:
https://xxx.baltimore.com:9985/saml_out
Receiver:
https://xxx.baltimore.com:9985/saml_in
Responder:
https://xxx.baltimore.com:9985/saml_responder
We can change the port number easily (as long as they're all the same) and
play DNS games to point all the names at the same actual host, but we can't
change the path.
- irving -
-----------------------------------------------------------------------------------------------------------------
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.
