What security is built into VirtUoso?
• Standard SQL-92 GRANT/REVOKE statements for DB users. • Access control lists for incoming clients based on source IP. • Each incoming connection can be passed to a hook function (a VirtUoso/PL stored procedure) for custom security measures. • SSL TLS is available for both ODBC and JDBC clients • x509 certificates for both ODBC and JDBC • For HTTP/DAV/SOAP Access • By default, requests for resources contained within the DAV repository are checked using HTTP/1.1 Digest authentication, using credentials stored in system users tables. • A UNIX-like permission mechanism is used to control access to contents of DAV repository, these permissions apply to users and groups of users. • BASIC and HTTP/1.1 Digest authentication. • Custom authentication methods may be implemented via an authentication hook API. Database: • Role Based Security Web Services: • WS-Security – enabling the use of symmetric and asymmetric encryption, digital signing, and identity authentication as defined by the WS-Sec
For ODBC/JDBC Access: • Standard SQL-92 GRANT/REVOKE statements for DB users. • Access control lists for incoming clients based on source IP. • Each incoming connection can be passed to a hook function (a Virtuoso/PL stored procedure) for custom security measures. • SSL TLS is available for both ODBC and JDBC clients • x509 certificates for both ODBC and JDBC • For HTTP/DAV/SOAP Access • By default, requests for resources contained within the DAV repository are checked using HTTP/1.1 Digest authentication, using credentials stored in system users tables. • A UNIX-like permission mechanism is used to control access to contents of DAV repository: these permissions apply to users and groups of users. • BASIC and HTTP/1.1 Digest authentication. • Custom authentication methods may be implemented via an authentication hook API. Database: • Role-Based Security Web Services: • WS-Security – enabling the use of symmetric and asymmetric encryption, digital signing, and identity authentication as
