Now I need how to figure out how to use Shiro with PKI and setup a custom
authentication with fuseki. Oh Joy. Thanks for your help Andy.

On Sat, Jan 10, 2015 at 6:11 PM, Trevor Donaldson <[email protected]>
wrote:

> Scratch that, I can use Jetty. I see that the jetty instance already has
> the shiro setup. I can just modify the shiro.ini file there. I think I am
> good to go.
>
> On Sat, Jan 10, 2015 at 5:52 PM, Trevor Donaldson <[email protected]>
> wrote:
>
>> Andy,
>>
>> Thanks the links worked. I have the war. The question I have is can I
>> overwrite the shiro.ini file? I see the war but everything is already
>> packaged.
>>
>> On Sat, Jan 10, 2015 at 11:00 AM, John A. Fereira <[email protected]>
>> wrote:
>>
>>>
>>> Thanks for the followup.  Your assurance that Fuseki2 is as capable as
>>> Fuseki1 was all I needed to do a bit more work with with.
>>>
>>> Regarding the comment about open source in general, I agree with the
>>> quote you posted.  I've been active in the open source community as a
>>> contributor for quite a long time.  I think it's important to note that
>>> "contributor" can mean many things, and not just writing code.  I was
>>> involved in an open source for higher education organization for many years
>>> as a documentation coordinates, took over maintenance of the conference
>>> management application used by their annual conferences and served on the
>>> program committee for those conferences for five years.  I did write some
>>> code for the project but that wasn't my major contribution.
>>>
>>> As I said, I had not looked at Fuseki2 in several weeks and not because
>>> my interaction was based only on hope.  I just have too many other projects
>>> I'm working on, almost all open source related, to be engaged as much as I
>>> like with various open source project I use.   Several of those projects
>>> are related to the Open Source Vivo semantic web application (
>>> vivoweb.org) for which I've not only made quite a few code
>>> contributions to the core code but am the official maintainer of a suite of
>>> data ingest tools (which use Jena) that are used by VIVO.  Additionally, I
>>> have built a configuration of Fuseki going back to when it was called
>>> Joseki and bundled it up and put it on our wiki so  that it could be used
>>> by the VIVO open source community.  In fact, just before I posted the
>>> message about Fuseki2 yesterday I had built a version from the latest
>>> Fuseki-1.1.1 code, put it on our wiki, and announced it's availability on
>>> our developers mailing list.
>>>
>>> Now that I know the status of Fuseki2 I'll be building a Fuseki2
>>> configuration as well and will be using it for another VIVO related
>>> project, but for the international Agriculture domain (I'm also the
>>> unofficial liaison for the use of VIVO internationally).
>>>
>>> -----Original Message-----
>>> From: Andy Seaborne [mailto:[email protected]]
>>> Sent: Saturday, January 10, 2015 6:55 AM
>>> To: [email protected]
>>> Subject: Re: Fuseki with a web.xml
>>>
>>> John,
>>>
>>> It's helpful if you could describe the specific features that didn't
>>> look complete and what you are looking for for your project.
>>>
>>> Monty Widenius (of MariaDB fame and a certain other database) put it
>>> succinctly: there are 3 ways to interact with an open source project:
>>> contribute; sponsor; hope.
>>>
>>> Laurens Rietveld contriuted integration on the query tab with his YASGUI
>>> javscript user interface for SPARQL endpoints.
>>>
>>>
>>> Fuseki2 is currently at least as capable as Fuseki1, which didn't have
>>> any admin.  It's the UI that's most new about Fuseki2.  For production
>>> use Fuseki1, had no UI. Fusek1 is deployed as a OS service (or some
>>> custom setup).
>>>
>>> Fuseki2 can run that way - it is compatible with Fuseki1 configuration.
>>>   It can also run from a WAR file dropped into a webapp conatiner such
>>> as Tomcat. The execution of SPARQL protocols is the same as Fuseki1,
>>> just cleaned up code.
>>>
>>> Fuseki2 adds security via Apache Shiro.  With Shiro, the admin functions
>>> are locked down to "localhost".
>>>
>>> Fuseki1 and Fuseki2 are both in the main Jena build and will be in the
>>> next release (before you ask "soon" - we can't set dates with any
>>> reliability because none of us have allocated Jena time; see
>>> "contribute; sponsor; hope").
>>>
>>> Not everything will be complete by Fuseki v2.0.0 but it will be at least
>>> as good a Fuseki1, unless you liked the plain old HTML pages. (there is
>>> no velocity templating anymore).
>>>
>>> "production ready" for open source is really when users consider it
>>> ready for their usage.  Personally, I'd run it in preference to Fuseki1
>>> now.  Fuseki1 remains to risk-reduce the transistion from my
>>> point-of-view.
>>>
>>>         Andy
>>>
>>> On 10/01/15 00:01, Trevor Donaldson wrote:
>>> > Not production ready, yet? Oh no. :-(
>>> > On Jan 9, 2015 6:59 PM, "John A. Fereira" <[email protected]> wrote:
>>> >
>>> >> I haven't looked at Fuseki2 in a few weeks but did finally get a
>>> version
>>> >> deployed with includes both a TDB and an SDB datastore, running under
>>> >> Tomcat.  I've got a project for which I'll need to use Fuseki and
>>> would
>>> >> like to use Fuseki2 but last time I used it there were still a number
>>> of
>>> >> things that didn't look complete, primarily with the admin
>>> interface.  How
>>> >> much progress has been made on that?  When you consider Fuseki2 to be
>>> >> "production ready"?
>>> >>
>>> >> -----Original Message-----
>>> >> From: Andy Seaborne [mailto:[email protected]]
>>> >> Sent: Friday, January 9, 2015 6:43 PM
>>> >> To: [email protected]
>>> >> Subject: Re: Fuseki with a web.xml
>>> >>
>>> >> On 09/01/15 22:11, Trevor Donaldson wrote:
>>> >>> Is it possible to have a Web.xml file with fuseki. I would like to
>>> >>> setup a filter element. Is this possible?
>>> >>>
>>> >>
>>> >> Yes.
>>> >>
>>> >> See Fuseki2 which is all web.xml driven including as a WAR file.  (It
>>> >> already uses a servlet filter to put Apache Shiro onto the dispatch
>>> patch
>>> >> for security handling.)
>>> >>
>>> >> Artifacts:
>>> >>
>>> >> jena-fuseki-server -- standalone jar
>>> >> jena-fuseki-war -- war file form
>>> >> jena-fuseki-dist -- for the binary distribution
>>> >>     somewhat like Fuseki1
>>> >>     see the webapp/ directory for the web.xml.
>>> >>
>>> >>          Andy
>>> >>
>>> >>
>>> >
>>>
>>>
>>
>

Reply via email to