[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [saml-dev] RE: Sigaba's config info
Yeah, our app is an encrypted mail decryptor/viewer thing, so we'd like it to be on https. -----Original Message----- From: Philpott, Robert [mailto:rphilpott@rsasecurity.com] Sent: Thursday, June 13, 2002 9:56 AM To: 'Trevor Perrin'; Jahan Moreh; Bhavna.Bhatnagar@Sun.COM; saml-dev@lists.oasis-open.org Subject: RE: Sigaba's config info Hi Trevor, I just wanted to double-check that you definitely want the application running on an https link. The interop spec indicated applications would be on non-SSL ports. I can understand that this one is a bit different, however. Thanks, 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: Trevor Perrin [mailto:Tperrin@sigaba.com] > Sent: Thursday, June 13, 2002 12:47 AM > To: Philpott, Robert; Jahan Moreh; Bhavna.Bhatnagar@Sun.COM; saml- > dev@lists.oasis-open.org > Subject: Sigaba's config info > > > Sigaba is only a content provider: > > application.sigaba.com -> 192.168.16.101 > receiver.sigaba.com -> 192.168.16.101 > > https://application.sigaba.com/application/ > https://receiver.sigaba.com/receiver/ > > We will redirect users to the transfer service ourselves per 1.6.D in the > interop document. In the TARGET parameter, there will be an extra path > element on the application URL, ie > "TARGET=https://application.sigaba.com/applicaton/SwFdOJwsM4KAkWo8kA/", > which we need to track session state. > > Trevor
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC