Before possibly reinventing a wheel, I'm wondering if anyone who uses application-level authentication on HTTP app servers has an elegant way of having a user log in once on one server and then be transparently logged in when accessing others. For example, I have an app server on port 8080 and another on port 8081. User XYZ logs in to port 8080, and then clicks on link pointing to the server on port 8081. The session-based login on 8080 isn't available to the app server on port 8081, so a second login is required.
Is there an admin function that allows retrieval of session information for a given user within a given app server, such that it could be used to determine whether a user should be considered "logged in" for purposes of the second app server? DS -- David Sewell, Editorial and Technical Manager ROTUNDA, The University of Virginia Press PO Box 400314, Charlottesville, VA 22904-4314 USA Email: [email protected] Tel: +1 434 924 9973 Web: http://rotunda.upress.virginia.edu/ _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
