From: <ml-...@fl...> - 2022-06-04 15:27:47
|
Hi Adam, for now, i've decided to put the credentials into the client.properties file. This works fine and allows for reading the credentials from the file system, but the user is restricted to just one set of credentials. Maybe, it would be a useful feature to add a command line option for custom client.properties files. There's already an option to point the Java Admin Client to a different conf.xml file to access different databases, but not to a different properties file. I'll take a look at the source code, maybe i manage to create a PR to implement this. Florian Am 24.05.2022 um 23:35 schrieb Adam Retter: > AFAIK the command line args are the only way at the moment. I would be > happy to see a PR that improves that though > > On Tue, 24 May 2022, 11:52 Florian Schmitt, > <mai...@fl... > <mailto:mai...@fl...>> wrote: > > Hi all, > > is there a different way to provide authentication credentials to the > Java Admin Client other than the command line parameters, e.g. read > the user credentials from the file system? My use case is writing a > bash script to import some resources into eXist using the Java Admin > Client. Currently, the only way to authenticate seems to be using the > command line parameters -u and -P, providing the db user credentials > in clear text in the bash script. This is quite ugly. Other tools, > e.g. cUrl, allow for using .netrc files with appropriate access > rights. Is something similar available fot the command line client? > What's the best practice for this use case? > > Thanks in advance! > Florian > > > _______________________________________________ > Exist-open mailing list > Exi...@li... > <mailto:Exi...@li...> > https://lists.sourceforge.net/lists/listinfo/exist-open > <https://lists.sourceforge.net/lists/listinfo/exist-open> > |