Re: [basex-talk] Using HTTP Digest Authentication in a RESTXQ services
Hi Omar, > As I see it there is no way of doing this selectively. Right, there is no such solution at the moment. We didn’t implement digest authentication via our permission layer so far, but it should definitely be possible (might be an interesting challenge… any volunteers out there?). Best, Christian > Like having the / > page not having authentication and /dba do authentication using some > other method. Or if I have some service where I need to decide at > runtime in XQuery code that I now would like to require the client to do > digest authentication. Digest authentication cannot be hooked to the > %perm annotation I think. > > Is that correct or am I missing something? > > Best regards > > Omar > > Am 14.02.2019 um 18:39 schrieb Christian Grün: > > Hi Omar, > > > > Digest authentication with RESTXQ should work out of the box. The > > following changes in the configuration may be required: > > > > • You’ll need to enable digest authentication in the web.xml > > configuration file [1] > > • By default, the admin user is enabled for RESTXQ requests. You’ll > > need to remove the corresponding entry [2] > > > > Best > > Christian > > > > [1] > > https://github.com/BaseXdb/basex/blob/9a089491894a01f9d8edb5d30e695f18b13bc9c4/basex-api/src/main/webapp/WEB-INF/web.xml#L93-L96 > > [2] > > https://github.com/BaseXdb/basex/blob/9a089491894a01f9d8edb5d30e695f18b13bc9c4/basex-api/src/main/webapp/WEB-INF/web.xml#L32-L35 > > > > > > > > On Thu, Feb 14, 2019 at 6:35 PM Omar Siam wrote: > >> Hi list! > >> > >> I just experimented a bit to see if there is an obvious way to use HTTP > >> digest authentication for some RESTXQ service I plan to write. I would > >> prefer not to reimplement the HTTP digest logic in XQuery. I thought > >> maybe there is a way to use the built in digest logic like for the REST > >> endpoint. I don't seem to get that to work. Any suggestions? > >> > >> Best regards > >> > >> Omar Siam > >>
Re: [basex-talk] Using HTTP Digest Authentication in a RESTXQ services
Hi and thanks for the quick response! Ok. Now I see how that works. As I see it there is no way of doing this selectively. Like having the / page not having authentication and /dba do authentication using some other method. Or if I have some service where I need to decide at runtime in XQuery code that I now would like to require the client to do digest authentication. Digest authentication cannot be hooked to the %perm annotation I think. Is that correct or am I missing something? Best regards Omar Am 14.02.2019 um 18:39 schrieb Christian Grün: Hi Omar, Digest authentication with RESTXQ should work out of the box. The following changes in the configuration may be required: • You’ll need to enable digest authentication in the web.xml configuration file [1] • By default, the admin user is enabled for RESTXQ requests. You’ll need to remove the corresponding entry [2] Best Christian [1] https://github.com/BaseXdb/basex/blob/9a089491894a01f9d8edb5d30e695f18b13bc9c4/basex-api/src/main/webapp/WEB-INF/web.xml#L93-L96 [2] https://github.com/BaseXdb/basex/blob/9a089491894a01f9d8edb5d30e695f18b13bc9c4/basex-api/src/main/webapp/WEB-INF/web.xml#L32-L35 On Thu, Feb 14, 2019 at 6:35 PM Omar Siam wrote: Hi list! I just experimented a bit to see if there is an obvious way to use HTTP digest authentication for some RESTXQ service I plan to write. I would prefer not to reimplement the HTTP digest logic in XQuery. I thought maybe there is a way to use the built in digest logic like for the REST endpoint. I don't seem to get that to work. Any suggestions? Best regards Omar Siam
Re: [basex-talk] Schema 1.1 validation and Xerces cta-full-xpath-checking?
Time and again I am amazed by the immediacy with which the BaseX team seizes opportunities for instantaneous improvement. The obsessive idea of agility, bugging ten-thousands of developing and managing heads, is dwarfed by the practice of BaseX. Am Donnerstag, 14. Februar 2019, 14:38:07 MEZ hat Christian Grün Folgendes geschrieben: Hi Daniel, hi George, With the latest snapshot of BaseX, XSD validation features can now be specified [1,2]. In addition to that, • I have removed the version argument. The most recent supported version XML Schema will now be used by default. • Two additional functions can be used to retrieve the applied processor and the supported version. Have fun, Christian [1] http://docs.basex.org/wiki/Validation_Module#XML_Schema_Validation [2] http://files.basex.org/releases/latest/ On Mon, Nov 19, 2018 at 5:07 PM Zimmel, Daniel wrote: > > Hi, > > is there any chance BaseX will support the cta-full-xpath-checking option > (see https://xerces.apache.org/xerces2-j/features.html)? Without it, schema > 1.1 validation is limited. > > I could not find any switches to configure Xerces features, but did find > someone mentioning it from two years ago: > https://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/msg08446.html > > Or have I missed something in the documentation? > > Regards, Daniel > > >
