A Java application will somehow need to securely be allowed to insert documents into the dbs of its callers, which are all other ML databases (several developers, QA, and production). ML executes http-get calls to Java with parameters for the jobs, Java does a bunch of work (this takes a while), and then finally inserts documents into the caller's db via XCC.
I have used semi-secure but convenient solutions for purely internal applications; however, this one will have to work over the Internet. My first thought was to have the caller generate a token, pass to Java SSL endpoint along with other parameters, Java calls XCC with limited credentials and the token, token is checked by caller and insertion is amped if it matches, then token is deleted. Will that suffice, or are there better, smarter ways to accomplish this? Thanks, Will _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
