RE: Single Sign On (implemented in CF)

2003-12-16 Thread d.a.collie
>> def worth reading (they were for me) if Jochem doesn't mind me posting them. The content of emails were worth reading for me I mean :-) -- dc [Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

RE: Single Sign On (implemented in CF)

2003-12-12 Thread Smith, Matthew P -CONT(CSC)
AIL PROTECTED] -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 10:35 AM To: CF-Talk Subject: RE: Single Sign On (implemented in CF) > > Just use the system with a recording proxy and see for > > yourself. > > Could you reco

RE: Single Sign On (implemented in CF)

2003-12-12 Thread Smith, Matthew P -CONT(CSC)
ETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: Jochem van Dieten [mailto:[EMAIL PROTECTED] Sent: Friday, December 12, 2003 9:35 AM To: CF-Talk Subject: Re: Single Sign On (implemented in CF) Smith, Matthew P -CONT(CSC) wrote: > >> Just use the s

RE: Single Sign On (implemented in CF)

2003-12-12 Thread Dave Watts
> > Just use the system with a recording proxy and see for > > yourself. > > Could you recommend one?  I'd like to delve a little deeper > with the stuff we are using here. Jochem recommended a Mozilla extension, which is good, but if you want something browser-independent and you're using Wind

Re: Single Sign On (implemented in CF)

2003-12-12 Thread Jochem van Dieten
Smith, Matthew P -CONT(CSC) wrote: > >> Just use the system with a recording proxy and see for yourself. > > Could you recommend one?  I'd like to delve a little deeper with the stuff we are using here. >   > Also, could you(or anyone else) recommend a good http sniffer?  I'm not sure if they are

RE: Single Sign On (implemented in CF)

2003-12-12 Thread Smith, Matthew P -CONT(CSC)
Dieten [mailto:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 11:16 AM To: CF-Talk Subject: Re: Single Sign On (implemented in CF) [EMAIL PROTECTED] wrote: >> >> Looking at Oracles Single Sign On Server (SSO Server) >> >> Seems to be saying that it can log into *

RE: Single Sign On (implemented in CF)

2003-12-12 Thread Smith, Matthew P -CONT(CSC)
Yes, and there is also Netigrity. http://www.netegrity.com/ I believe(don't quote me on this) that oblix had better certification for government security requirements.  It does not necessarily mean that Netegrity is less secure, they just haven't done the required paperwork as of yet.  I do n

RE: Single Sign On (implemented in CF)

2003-12-11 Thread Smith, Matthew P -CONT(CSC)
y Center (NETPDTC) (850)452-1001 ext. 1245 [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 11, 2003 12:20 PM To: CF-Talk Subject: RE: Single Sign On (implemented in CF) Explained well enough for even me to unde

RE: Single Sign On (implemented in CF)

2003-12-11 Thread d.a.collie
Explained well enough for even me to understand :-)  Superb I'll digest the info and put it to those above tomorrow as an option >> I would be interested in anything more detailed you can dig up on SSO. No probs, will let you know what we find out and any URLs/Docs that we find that are

Re: Single Sign On (implemented in CF)

2003-12-11 Thread Jochem van Dieten
[EMAIL PROTECTED] wrote: > >> You might want to take a look at http://a-select.surfnet.nl/ > > Thank you... currently digesting now > > As far as I can see at the moment, all apps need to use A-Select API > though... No, the webserver needs to have the A-Select API. It is just an ISAPI f

RE: Single Sign On (implemented in CF)

2003-12-11 Thread d.a.collie
Again thanks for your insights Jochem, much appreciated :-) >> It looks like the visitor is redirected to the SSO server, >> which does authentication and then redirects the user >> back, probably with some identification URL variable. Would this not mean that it was the SSO server that was au

Re: Single Sign On (implemented in CF)

2003-12-11 Thread Jochem van Dieten
[EMAIL PROTECTED] wrote: >> >> Looking at Oracles Single Sign On Server (SSO Server) >> >> Seems to be saying that it can log into *any* external web app (given >> that it knows the username and password and it is an HTML form) and >> then remember the user upon return to the portal application