If the URL root is the same, you can use cookies to pass an authentication token (that you create yourself) among the applications.
If they are not- you have to pass the authentication token in plaintext over the query string.
The advantage of using a QUery TOken is you can use a GUID (for example) and use that to point into a database that holds the real authenticaion information. a GUID is complex enough that the user wouldn't be able to fake it to get access. You can timeout the token in the backend database to be valid for X time. (or X time after the last contact). This secures the information and gives you the "single signon" you need.
Hal Levy
Web Developer, PDI Inc.
NOT a Wiley/Wrox Employee
|