sounds very useful. however it doesn't seem to be working :( after adding SPARQL_UPDATE to SPARQL in the conductor UI i get this from the endpoint:
42000 Error SR186: No permission to execute procedure DB.DBA.SPARQL_INSERT_DICT_CONTENT. SPARQL query: define sql:signal-void-variables 1 insert in graph <http://dbtune.org/cmn/resource> {<http://dbtune.org/cmn/resource/kurtjx> <http://purl.org/onotology/classicalmusicnav#influencedBy> <http://dbtune.org/cmn/resource/WAGN>} any idea what i'm missing? cheers, kurt j On Tue, Feb 3, 2009 at 12:27 PM, Hugh Williams <hwilli...@openlinksw.com> wrote: > Kurt, > On 3 Feb 2009, at 11:19, Kurt J wrote: > >>> Do you have the SPARQL_SPONGE role enabled for SQL USER "SPARQL" ? This >>> is >>> ROLE isn't granted by default for security reasons. >> >> under System Admin -> User Accounts -> SPARQL -> Account Roles -> Selected >> >> SPARQL_SELECT >> SPARQL_SPONGE >> >> sort of unrelated question, adding the role SPARQL_UPDATE to SPARQL >> would allow _anyone_ to execute an update command thru the sparql >> interface? >> > > [Hugh] Yes, it would, which is why we have the SPARQL_SPONGE role to allow > sponger only operations to be able to update, keeping the SPARQL endpoint > secure unless you specifically grant the SPARQL_UPDATE role to it. > > Regards > Hugh > >> -kurt > >
