Sairam and Sharon, thank you both for taking the time to help me. So the next thing for me to do is write an authenticator, then.
Again, thank you very much. /jan Sharon Lucas wrote: > Thanks to Sairam for responding to your question as well. > > I just wanted to reiterate that the authenticator must be installed on > each machine in order for user trust to be used. Authentication data is > sent along with other information when submitting a STAF service request > to a remote machine. The remote machine also performs authentication > using this data (as another check to prevent any misuse). Note that a > STAF authenticator can specify that it requires a secure connection so > that authentication data is only sent if the data is being sent via the > STAF secure TCP/IP connection provider. > > You can write your own STAF authenticator service instead of using the > sample authenticator that we provide on SourceForge. For example, we have > written our own STAF authenticator service that authenticates using my > company's Intranet Password authenticate API to authenticate using our > existing intranet userids and credentials.. Our authenticator (which is > only available within my company) requires using the STAF secure TCP/IP > connection provider for added protection. > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
