. . . "ValWhatWhyHow" . "ValWhatWhyHow" . . . "e8587ddad0382285855c850eb800f4b3" . "2017-06-13T06:07:11.645591"^^ . . . "2017-06-13T06:07:11.645591"^^ . "2017-06-13T06:07:11Z" . . . "2017-06-13T06:07:11Z" . . . . "ValWhatWhyHow" . . . . . . "---+ Virtuoso Authentication Layer (VAL) - What, Why and How\n\n%TOC%\n\n---++ What Is the Virtuoso Authentication Layer (VAL)?\n\nVAL, the Virtuoso Authentication Layer, is an open-standards-based, multi-protocol authentication layer, \nthat provides fine-grained, attributed-based access controls (ABAC) to protected resources (HTTP-accessible \ndocuments, folders, services [via their endpoints], and SPARQL named graphs). In a nutshell, this solution \nuses logic, expressed in the form of entity relationships, to address issues such as identity, authorization, \nand restriction.\n\nThe key components of this solution are:\n\n * HTTP URI (Hyperlink) based Entity Identifiers (Names)\n * TLS based data transmission\n * RDF Language based Statements representing Entity Relationships and\n Entity Relationship Types\n * Vocabulary of terms from publicly accessible vocabularies such as \n * <[[http://www.w3.org/ns/auth/acl#][http://www.w3.org/ns/auth/acl#]]>\n * <[[http://www.openlinksw.com/ontology/acl#][http://www.openlinksw.com/ontology/acl#]]>\n * <[[http://www.openlinksw.com/ontology/restrictions#][http://www.openlinksw.com/ontology/restrictions#]]>\n * <[[http://www.openlinksw.com/schemas/cert#][http://www.openlinksw.com/schemas/cert#]]>\n * Entity Relationship Type Semantics\n\nCollectively, the components above enable:\n\n * Unambiguous Naming\n * Identity Claims Construction\n * Identity Claims Verification\n * Resource Access Rules (Authorizations) Creation and Evaluation\n * Resource Access Rate Rules (Restrictions) Creation and Evaluation\n \n--++ Why Is VAL Important?\n\nAs access to data grows across users, private networks, public networks, and hybrid network dimensions, \nthere is an ever-increasing demand for controlled access to this data, in a manner that covers a variety \nof operational and social dimensions. It is no longer feasible to secure data using naive literal \nidentification that doesn't attend to entity relationship realities reflected in the nature of different \nkinds of entity relationships.\n\n--++ How Do I Use VAL?\n\n---+++ Prerequisites\n\n * Virtuoso Commercial Edition Instance\n * Virtuoso Authentication Layer (VAL) add-on module installation\n * Virtuoso Faceted Browser — optional; recommended for verification and troubleshooting\n * X.509 Certificates for Agents (Virtuoso Web Server and Client Software [e.g., SSH, HTTPS, ODBC, JDBC, ADO.NET applications]) that will communicate over TLS \n * X.509 Certificates for Application Users ? optional; not necessary whn Identity Delegation is in use\n\n---+++ Authorization Scoping\n\nEvery resource type protected by VAL is associated with a distinct ACL scope. Examples include:\n\n * Sponger - for the Virtuoso Sponger Middleware Layer\n * SpongerCartridges - for specific Sponger Cartridges (for finer granularity control of \n access to the Sponger)\n * Query - for Query Services (SPARQL or SQL)\n * WebDAV - for all folders and documents accessible via WebDAV or \n Linked Data Profile (LDP) protocols\n * OAuth - for OAuth protocol\n * Private Named Graphs -- for internal RDF documents controlled by the Virtuoso Quad Store\n * Basic Entity Description Services\n * Advanced Faceted Browsing based Entity Description Services\n * PivotViewer Data Visualization\n * URI Shortener\n * Custom Scopes created for custom applications\n\n---+++ Virtuoso Realms\n\nAs a hybrid data server, Virtuoso provides access to data across two distinct (but interlinked) functionality \nrealms: HTTP and SQL. Thus, configuring VAL requires creation of Authorization and Restrictions rules that \ntarget each of the aforementioned realms, individually.\n\nVAL Authorizations apply to HTTP and/or SQL realms distinctly. Basically, you have an ACL Scope by Virtuoso \nRealms matrix per basic unit of ABAC functionality.\n\n\n

Conductor's VAL Configuration UI

\n\n---+++ Creating an ABAC ACL\n\nYou achieve this by writing a collection of RDF language statements to a special VAL system named graph. \nThese statements describe an instance of an authorization, and where additional restrictions apply they \nare also used to describe resource usage rate restrictions.\n\n----++++ Example of ABAC ACL\n\n\n## Declaring an Authorization granting read-access to the named graph identified by the IRI \n## \n \nSPARQL\nPREFIX oplacl: \nPREFIX acl: \n\nWITH\n \nINSERT\n {\n <#PrivateNamedGraphRule1> \n a acl:Authorization ;\n foaf:maker ;\n oplacl:hasAccessMode oplacl:Read ;\n acl:accessTo ;\n acl:agent ;\n oplacl:hasScope oplacl:PrivateGraphs ;\n oplacl:hasRealm oplacl:DefaultRealm .\n };\n\n\n---+++Protecting an HTTP Realm (aka DefaultRealm) Service\n\nTo protect HTTP Services provided by a Virtuoso instance such as: SPARQL endpoints, WebDAV \nand LDP file systems, Faceted Browsing, Sponger Entity Description Pages, PivotViewer, \nURL Shortener, and SPARQL/SQL Interactive Query Builder, etc., you need create the following:\n\n 1 Describe your ACL using RDF Statements based on terms from the \n <[[http://www.w3.org/ns/auth/acl#][http://www.w3.org/ns/auth/acl#]]>, \n <[[http://www.openlinksw.com/ontology/acl#][http://www.openlinksw.com/ontology/acl#]]>, \n and <[[http://www.openlinksw.com/ontology/restrictions#][http://www.openlinksw.com/ontology/restrictions#]]> \n vocabularies.\n 1 Load your ACLs to the Virtuoso Quad Store hosted VAL system named graph using one of the following:\n * Virtuoso's RDF document loader\n * SPARQL\n * SPARQL inside SQL - via Conductor or command-line ISQL interfaces.\n 1 Test your ACL\n\n---++++ Troubleshooting ACLs on HTTP Realm\n\nIf your ACL doesn't perform as expected please check the following:\n\n * Your desired ACL scope is enabled - this will be visible via the Conductor Configuration URI \n for VAL or it can be looked up via its HTTP URI using the Faceted Browser or SPARQL.\n * The enabled ACL scope is associated with the DefaultRealm - this is what \n binds an ACL to the HTTP functionality realm and this will be visible via the Conductor Configuration \n UI for VAL or it can be lookedup via its HTTP URI using the Faceted Browser or SPARQL.\n\n---+++ Protecting a SQL Realm (aka SqlRealm) Service\n\nTo protect SQL Services provided by a Virtuoso instance (e.g., ODBC, JDBC, ADO.NET, OLE-DB connectivity and \naccess; SPASQL (SPARQL inside SQL); etc.), you need to take the following steps:\n\n 1 Create RDF statements, based on terms from the \n <[[http://www.w3.org/ns/auth/acl#][http://www.w3.org/ns/auth/acl#]]>, \n <[[http://www.openlinksw.com/ontology/acl#][http://www.openlinksw.com/ontology/acl#]]>, and \n <[[http://www.openlinksw.com/ontology/restrictions#][http://www.openlinksw.com/ontology/restrictions#]]> \n vocabularies, that describe each of the following\n * a SQL Realm access authorization, for example —\n\n-- SQLRealm ACL\n-- Cleanup\n\nSPARQL\nPREFIX oplacl: \nPREFIX acl: \n\nWITH \n \nDELETE \n {\n <#WebIDTLSSQLAccessRule1> ?p ?o . \n };\n\n-- ACL Definition \n\n-- SQL Access Privileges Grant to a Specific WebID --\n\nSPARQL\nPREFIX oplacl: \nPREFIX acl: \nPREFIX foaf: \n\nWITH GRAPH \n \nINSERT \n {\n <#WebIDTLSSQLAccessRule1> \n a acl:Authorization ;\n foaf:maker ;\n rdfs:label \"SQL Realm Access Authorization ACL\" ;\n rdfs:comment \"\"\"Mandatory ACL for granting access to SQL Realm which then enables ODBC, JDBC, ADO.NET, OLE-DB compliant\n application access, subject to Agent & User Identity.\"\"\" ;\n oplacl:hasAccessMode oplacl:Read ;\n acl:accessTo ;\n acl:agent ,\n ,\n ,\n , \n ;\n oplacl:hasScope oplacl:Query ;\n oplacl:hasRealm oplacl:SqlRealm .\n };\n\n\n * a SQL Realm usage rate per second restriction, for example —\n\n-- SQL Query Access Restrictions (SQLRealm re. ODBC, JDBC, ADO.NET) -- \n-- Query Request Rate\n-- Cleanup\n\nSPARQL \n\nPREFIX oplacl: \nPREFIX acl: \nPREFIX foaf: \nPREFIX oplrest: \n\nWITH GRAPH \n \nDELETE\n {\n <#IDMyOpenLinkTLSSQLAccessRestriction1> ?p ?o . \n };\n\n-- Restriction Definition\n\nSPARQL \n\nPREFIX oplacl: \nPREFIX acl: \nPREFIX foaf: \nPREFIX oplrest: \n\nWITH GRAPH\n \nINSERT\n {\n <#IDMyOpenLinkTLSSQLAccessRestriction1> \n a oplrest:Restriction ;\n foaf:maker ;\n rdfs:label \"SQL Realm Query Rate Restriction\" ;\n rdfs:comment \"\"\"Mandatory Restriction for metering Query Request Rates per second.\"\"\" ;\n oplrest:hasRestrictedResource ;\n oplrest:hasMaxValue \"100\"^^xsd:integer ;\n acl:agent ,\n ,\n ,\n , \n ;\n oplacl:hasRealm oplacl:SqlRealm .\n};\n\n\n * a SQL Realm Max Rows per query result set [solution] restriction, for example —\n\n-- Query Results Size \n-- Cleanup\n\nSPARQL \n\nPREFIX oplacl: \nPREFIX acl: \nPREFIX foaf: \nPREFIX oplrest: \n\nWITH GRAPH\n \nDELETE\n {\n <#IDMyOpenLinkTLSSQLAccessRestriction2> ?p ?o . \n };\n\n\n-- Restriction Definition\nSPARQL \n\nPREFIX oplacl: \nPREFIX acl: \nPREFIX foaf: \nPREFIX oplrest: \n\nWITH GRAPH\n \nINSERT\n {\n <#IDMyOpenLinkTLSSQLAccessRestriction2> \n a oplrest:Restriction ;\n foaf:maker ;\n rdfs:label \"SQL Realm Resultset [Query Solution] Size Restriction\" ;\n rdfs:comment \"\"\"Mandatory Restriction for restrictng maximum size of query resultsets [solutions].\"\"\" ;\n oplrest:hasRestrictedResource ;\n oplrest:hasMaxValue \"200\"^^xsd:integer ;\n acl:agent ,\n ,\n ,\n , \n ;\n oplacl:hasRealm oplacl:SqlRealm .\n};\n\n\n 1 Load your ACLs to the Virtuoso Quad Store hosted VAL system named graph using one of the following:\n * Virtuoso's RDF document loader\n * SPARQL\n * SPARQL inside SQL - via Conductor or command-line ISQL interfaces.\n 1 Test your ACL\n\n---++++ Troubleshooting ACLs on SQL Realm \n\nIf your ACL doesn't perform as expected, please check the following:\n\n * Existence of an Authorization - You can look up the existence of your Authorization via its HTTP URI using the \n Faceted Browser or SPARQL.\n * Existence of a Restriction - You can look up the existence of your Restriction via its HTTP URI using the \n Faceted Browser or SPARQL.\n * Your desired ACL scope is enabled - this will be visible via the Conductor Configuration UI for VAL or \n it can be looked up via its HTTP URI using the Faceted Browser or SPARQL.\n * The enabled ACL scope is associated with the DefaultRealm - this is what binds an ACL \n to the HTTP functionality realm and will be visible via the Conductor Configuration UI for VAL or it can \n be looked-up via its HTTP URI using the Faceted Browser or SPARQL.\n\n---\n\n---++ Further Reading\n\n * [[ValQuickStartGuide][Virtuoso Authentication Layer - ACL System Quickstart Guide]]\n\n---" . . .