Open jakubklimek opened 10 years ago
On 2/13/14 9:38 AM, jakubklimek wrote:
Would it be possible to introduce another set of variables for sparql-auth?
I think it is a common case where we have a public endpoint which we need limited for anonymous usage, but for internal querying and updates (sparql-auth) we need it less restricted. Ideally, this setting would be per user or user role, but differentiating by anonyomous and logged in users would be enough.
— Reply to this email directly or view it on GitHub https://github.com/openlink/virtuoso-opensource/issues/137.
That's delivered via our fine-grained ACL functionality. This functionality is part of the commercial edition only, though.
Regards,
Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter Profile: https://twitter.com/kidehen Google+ Profile: https://plus.google.com/+KingsleyIdehen/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Would it be possible to introduce another set of variables for sparql-auth?
I think it is a common case where we have a public endpoint which we need limited for anonymous usage, but for internal querying and updates (sparql-auth) we need it less restricted. Ideally, this setting would be per user or user role, but differentiating by anonyomous and logged in users would be enough.