<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head profile="http://internetalchemy.org/2003/02/profile">
<link rel="foaf" type="application/rdf+xml" title="FOAF" href="http://www.openlinksw.com/dataspace/uda/about.rdf" />
<link rel="schema.dc" href="http://purl.org/dc/elements/1.1/" />
<meta name="dc.title" content="15. Web Services" />
<meta name="dc.subject" content="15. Web Services" />
<meta name="dc.creator" content="OpenLink Software Documentation Team ; " />
<meta name="dc.copyright" content="OpenLink Software, 1999 - 2009" />
<link rel="top" href="index.html" title="OpenLink Virtuoso Universal Server: Documentation" />
<link rel="search" href="/doc/adv_search.vspx" title="Search OpenLink Virtuoso Universal Server: Documentation" />
<link rel="parent" href="webservices.html" title="Chapter Contents" />
<link rel="prev" href="wsdl.html" title="WSDL" />
<link rel="next" href="voauth.html" title="OAuth Support" />
<link rel="shortcut icon" href="../images/misc/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" type="text/css" href="doc.css" />
<link rel="stylesheet" type="text/css" href="/doc/translation.css" />
<title>15. Web Services</title>
<meta http-equiv="Content-Type" content="text/xhtml; charset=UTF-8" />
<meta name="author" content="OpenLink Software Documentation Team ; " />
<meta name="copyright" content="OpenLink Software, 1999 - 2009" />
<meta name="keywords" content="" />
<meta name="GENERATOR" content="OpenLink XSLT Team" />
</head>
<body>
<div id="header">
<a name="vfoafssl" />
<img src="../images/misc/logo.jpg" alt="" />
<h1>15. Web Services</h1>
</div>
<div id="navbartop">
<div>
<a class="link" href="webservices.html">Chapter Contents</a> | <a class="link" href="wsdl.html" title="WSDL">Prev</a> | <a class="link" href="voauth.html" title="OAuth Support">Next</a>
</div>
</div>
<div id="currenttoc">
<form method="post" action="/doc/adv_search.vspx">
<div class="search">Keyword Search: <br />
<input type="text" name="q" /> <input type="submit" name="go" value="Go" />
</div>
</form>
<div>
<a href="http://www.openlinksw.com/">www.openlinksw.com</a>
</div>
<div>
<a href="http://docs.openlinksw.com/">docs.openlinksw.com</a>
</div>
<br />
<div>
<a href="index.html">Book Home</a>
</div>
<br />
<div>
<a href="contents.html">Contents</a>
</div>
<div>
<a href="preface.html">Preface</a>
</div>
<br />
<div class="selected">
<a href="webservices.html">Web Services</a>
</div>
<br />
<div>
<a href="soap.html">SOAP</a>
</div>
<div>
<a href="wsdl.html">WSDL</a>
</div>
<div class="selected">
<a href="vfoafssl.html">WebID Protocol Support</a>
<div>
<a href="#vfoafsslx509" title="x.509 certificate">x.509 certificate</a>
<a href="#vfoafsslsethttps" title="Setting up Virtuoso HTTPS">Setting up Virtuoso HTTPS</a>
<a href="#vfoafsslff" title="Setting Up Firefox">Setting Up Firefox</a>
<a href="#vfoafsslconf" title="Configuring ODS Account to use WebID Protocol">Configuring ODS Account to use WebID Protocol</a>
<a href="#vfoafssltst" title="Testing the setup">Testing the setup</a>
<a href="#vfoafsslacl" title="WebID Protocol ACLs">WebID Protocol ACLs</a>
<a href="#sparqloauthendpointfoafsslsparql" title="SPARQL-SSL based Endpoint">SPARQL-SSL based Endpoint</a>
<a href="#vfoafsslcacondt" title="CA Keys Import using Conductor">CA Keys Import using Conductor</a>
<a href="#vfoafsslst509issuer" title="Set Up X.509 certificate issuer, HTTPS listener and generate ODS user's certificates">Set Up X.509 certificate issuer, HTTPS listener and generate ODS user's certificates</a>
<a href="#vfoafsslsethttpsfoafsll" title="WebID Protocol ODBC Login">WebID Protocol ODBC Login</a>
</div>
</div>
<div>
<a href="voauth.html">OAuth Support</a>
</div>
<div>
<a href="vwsssupport.html">WS-Security (WSS) Support in Virtuoso SOAP Server</a>
</div>
<div>
<a href="ws-routing.html">Web Services Routing Protocol (WS-Routing)</a>
</div>
<div>
<a href="warm.html">Web Services Reliable Messaging Protocol (WS-ReliableMessaging)</a>
</div>
<div>
<a href="vwstrust.html">Web Services Trust Protocol (WS-Trust)</a>
</div>
<div>
<a href="xmlxmla.html">XML for Analysis Provider</a>
</div>
<div>
<a href="xmlrpc.html">XML-RPC support</a>
</div>
<div>
<a href="syncml.html">SyncML</a>
</div>
<div>
<a href="uddi.html">UDDI</a>
</div>
<div>
<a href="expwsmodules.html">Exposing Persistent Stored Modules as Web Services</a>
</div>
<div>
<a href="vsmx.html">Testing Web Published Web Services</a>
</div>
<div>
<a href="bpel.html">BPEL Reference</a>
</div>
<div>
<a href="xsql.html">XSQL</a>
</div>
<br />
</div>
<div id="text">
<a name="vfoafssl" />
<h2>15.3. WebID Protocol Support</h2>
<p>WebID Protocol is an authentication and authorization protocol that links a "Web ID" or
"<a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess">Personal URI</a>"
to a public key to create a global, decentralized, distributed, and secure authentication system that
functions with existing browsers.</p>
<p>WebID Protocol uses PKI standards - usually thought of as hierarchical trust management tools -
<a href="http://blogs.sun.com/bblfish/entry/foaf_ssl_pki_and_the">in a decentralized web-of-trust way</a>.
The web of trust is built using semantic web vocabularies (particularly <a href="http://www.foaf-project.org/">FOAF</a>) published in RESTful manner to
form Linked Data.</p>
<p>Based on well known existing standards, WebID Protocol is currently in development, and is being discussed
on the <a href="http://lists.foaf-project.org/mailman/listinfo/foaf-protocols">FOAF protocols mailing list</a>.</p>
<p>For the most recent description of the protocol, read the one-page
"<a href="http://blogs.sun.com/bblfish/entry/foaf_ssl_adding_security_to">WebID Protocol: Adding Security to
Open Distributed Social Networks</a>". For a more detailed explanation of how the authentication works,
see "<a href="http://blogs.sun.com/bblfish/entry/more_on_authorization_in_foaf">WebID Protocol: Creating a Web of Trust without Key Signing Parties</a>".</p>
<p>Automatic discovery of interpersonal trust relationships enables automatic application of appropriate
permissions.</p>
<p>In other words, data owners can set fuzzy permissions like "only let my friends see this" or "only
let my family edit this." Applications can discover the relationships between the data owner and the data
requester/user, and permit (or disallow) any attempted actions, without needing the data owner to explicitly
set permissions for each potential user.</p>
<p>One example might be a parent setting permissions on a photo gallery, to permit viewing only by
"immediate family". The parent need not list each and every such relative specifically for this
application - and need not add new permissions for a new family member (whether by marriage, birth, or
otherwise), though they do need to be added to the owner's FOAF. When a new user comes and asks to see
the pictures, the gallery application would check the relationships declared by each person (the owner
and the visitor), and if they matched up (in other words, the visitor could not get in simply by claiming
a family relationship; the relationship must be confirmed by the owner's FOAF data), the pictures would
be shown.</p>
<a name="vfoafsslx509" />
<h3>15.3.1. x.509 certificate</h3>
<p>The WebID Protocol consumer needs an x509 certificate with v3 extension "Subject Alternate Name". This
attribute is used for the owner's Web ID. For testing purposes we used OpenSSL demo CA to generate such
certificates. If you are not using the OpenSSL demo CA, you must first setup a self-signed CA; read
OpenSSL documents on how to do this.</p>
<ol>
<li>Add the following line to the [usr_cert] section of the openssl.cnf file:
<div>
<pre class="programlisting">
subjectAltName=$ENV::ALTNAME
</pre>
</div>
</li>
<li>Set the environment variable ALTNAME to the owner's Web ID, e.g.,
<div>
<pre class="programlisting">
export ALTNAME=URI:http://localhost/dataspace/person/myname#this
</pre>
</div>
</li>
<li>Make a self-signed certificate, e.g.,
<div>
<pre class="programlisting">
$ CA.pl -newreq (follow the dialog)
$ CA.pl -sign
</pre>
</div>
</li>
<li>When asked to commit the certificate, make sure you see several lines above, like:
<div>
<pre class="programlisting">
X509v3 Subject Alternative Name:
URI:http://localhost/dataspace/person/myname#this
</pre>
</div>
</li>
<li>If your browser wants a PKCS#12 bundle, you must make one:
<div>
<pre class="programlisting">
$ openssl pkcs12 -export -in newcert.pem -inkey newkey.pem -out mycert.p12
</pre>
</div>
</li>
<li>Rename newcert.pem and newkey.pem, to mycert.pem and mykey.pem for example.
The PEM format of the certificate will be needed below.</li>
</ol>
<br />
<a name="vfoafsslsethttps" />
<h3>15.3.2. Setting up Virtuoso HTTPS</h3>
<p>To enable the HTTPS listener, you will need another certificate. Existing certificates may not
have Subject Alternate Name, so you may want to generate one as in the previous section.</p>
<ol>
<li>The next step is to move newcert.pem, newkey.pem, and cacert.pem into the server's
working directory. In our test case, we put the keys in a 'keys' sub-directory, and added the following
lines to the [HTTPServer] section of the Virtuoso INI file, virtuoso.ini:
<div>
<pre class="programlisting">
SSLPort = 4443
SSLCertificate = ./keys/localhost.cert.pem
SSLPrivateKey = ./keys/localhost.key.pem
X509ClientVerifyCAFile = ./keys/localhost.ca.pem
X509ClientVerify = 1
X509ClientVerifyDepth = 15
</pre>
</div>
</li>
<li>Also in the Virtuoso INI file, in the [URIQA] section, DefaultHost (localhost:8890 below)
must be edited to correspond to the DNS-resolvable host name ("CNAME") of the Virtuoso host, combined
with the ServerPort as set in the [HTTPServer] section of the same INI file.
<div>
<pre class="programlisting">
[URIQA]
DynamicLocal = 1
DefaultHost = localhost:8890
</pre>
</div>
<p>For instance, if the CNAME of the host is virtuoso.example.com, and the ServerPort is 4321,
the DefaultHost should be set to virtuoso.example.com:4321</p>
<div>
<pre class="programlisting">
[URIQA]
DynamicLocal = 1
DefaultHost = virtuoso.example.com:4321
</pre>
</div>
</li>
<li>Start the Virtuoso server, and look at the log file. Once HTTPS is up, you should see
something like:
<div>
<pre class="programlisting">
HTTPS Using X509 Client CA ....
HTTPS/X509 server online at 4443
</pre>
</div>
</li>
</ol>
<br />
<a name="vfoafsslff" />
<h3>15.3.3. Setting Up Firefox</h3>
<ol>
<li>
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting Up Firefox" src="../images/ui/foafssl1.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.3.1. Setting Up Firefox</td>
</tr>
</table>
</li>
<li>Click the "Add exception" button and enter the address of the HTTPS server you've just
configured, i.e., https://virtuoso.example.com:4443/</li>
<li>Click OK, and confirm the exception.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting Up Firefox" src="../images/ui/foafssl2.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.3.1. Setting Up Firefox</td>
</tr>
</table>
</li>
<li>Click to the "Your Certificates" tab, and import mycert.p12.</li>
</ol>
<br />
<a name="vfoafsslconf" />
<h3>15.3.4. Configuring ODS Account to use WebID Protocol</h3>
<ol>
<li>Log in to your ODS account, and edit your profile. </li>
<li>Click to the Security Tab, and scroll to the bottom, where you will
find the X.509 certificate entry area. </li>
<li>Copy and paste the PEM format of the certificate (i.e., the content of mykey.pem,
from earlier). </li>
<li>Press "Save Certificate" button, and you are set.</li>
</ol>
<br />
<a name="vfoafssltst" />
<h3>15.3.5. Testing the setup</h3>
<p>To test, we recommend <a href="http://www.mozilla.com/firefox/">Firefox</a> v3 with the
<a href="https://addons.mozilla.org/en-US/firefox/addon/5596">Tabulator extension</a>. Firefox must
be set to ask for RDF, as instructed in the <a href="http://dig.csail.mit.edu/2007/tab/">Tabulator documentation</a>.
</p>
<ol>
<li>Enter an ODS user's URI in the address bar.</li>
<li>You should see a protected document's URI. Note that there is no specific "address" data seen:
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Testing the setup" src="../images/ui/foafssl3.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.5.1. Testing the setup</td>
</tr>
</table>
</li>
<li>When clicked, the browser will ask the user to select a certificate (note: certificate details
are erased in the picture below).
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Testing the setup" src="../images/ui/foafssl4.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.5.1. Testing the setup</td>
</tr>
</table>
</li>
<li>Now the protected document includes the private address data alongside the previously visible
public data!
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Testing the setup" src="../images/ui/foafssl5.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.5.1. Testing the setup</td>
</tr>
</table>
</li>
</ol>
<br />
<a name="vfoafsslacl" />
<h3>15.3.6. WebID Protocol ACLs</h3>
<p>You can <a href="rdfsparql.html#sparqloauthendpointfoafssl">set WebID Protocol ACLs</a> from the Virtuoso Authentication Server UI. </p>
<br />
<a name="sparqloauthendpointfoafsslsparql" />
<h3>15.3.7. SPARQL-SSL based Endpoint</h3>
<p>See details how to <a href="rdfsparql.html#sparqloauthendpointfoafssl">create and use a SPARQL-SSL based Endpoint</a>.</p>
<br />
<a name="vfoafsslcacondt" />
<h3>15.3.8. CA Keys Import using Conductor</h3>
<p>The Virtuoso Conductor allows easy import of user-level CA (Certificate Authority) Keys through
System Admin -> User Accounts -> Edit.</p>
<p>The dba user (typically) or other users may need CA keys to execute different services.</p>
<p>For ODS, the dba user must import a certificate with primary key and with name id_rsa. The process
takes the following steps:</p>
<ol>
<li>A signing authority (e.g., RSA Labs) generates a site certificate.</li>
<li>The site certificate is used to generate certificates for ODS users.</li>
<li>The site certificate is imported with name id_rsa for user dba using the Conductor.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Conductor CA Keys Import" src="../images/ui/foafssl27.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.8.1. Conductor CA Keys Import</td>
</tr>
</table>
</li>
<li>As a result, the ODS user certificates can be authenticated against the site certificate.</li>
</ol>
<p>If there is a service that requires a different key, the Conductor can be used to import another
certificate for the relevant user.</p>
<p>You can use a Key from a global signing authority or produce a self-signed key using the <a href="http://s3.amazonaws.com/opldownload/uda/vad-packages/6.1/virtuoso/conductor_dav.vad">Virtuoso Conductor</a>.</p>
<p>Details and more information how to generate the key see in the next section.</p>
<br />
<a name="vfoafsslst509issuer" />
<h3>15.3.9. Set Up X.509 certificate issuer, HTTPS listener and generate ODS user's certificates</h3>
<p>The following Step-by-Step guide walks you through set up of an X.509 certificate issuer and HTTPS listener, and generation of ODS user certificates.</p>
<ol>
<li>Install <a href="http://download.openlinksw.com/packages/5.0/virtuoso/ods_framework_dav.vad">ODS</a> and <a href="http://s3.amazonaws.com/opldownload/uda/vad-packages/6.1/virtuoso/conductor_dav.vad">Virtuoso Conductor</a> VAD packages.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl6.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Go to the http://cname:port/identity_manager URL, enter the DBA user credentials in the dialog presented.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl7.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Enter the Issuer details and click generate.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl8.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Go to Conductor -> Web Application Server -> Virtual Domains & Directories,
and add a new listener.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl9.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Edit the new listener, and generate new key.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl10.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Go to Packages list and select Configure for ODS Framework.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl11.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Select Create New Endpoint.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl12.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Enter the home path for ODS, and save.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl13.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>The new endpoint should now appear in the endpoint list.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl14.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Go to the HTTPS site, e.g., https://cname:port/ods; in our example, https://localhost:4433/ods/.
If Firefox is used, it will complain that the certificate is not valid, so we must register the site's
certificate.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl15.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>In Firefox certificate manager, in Site's certificates, add an exception.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl16.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Confirm exception.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl17.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Return to ODS site, and register new user.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl18.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Edit the user's profile and enter his/her name(s). If this step is skipped, the certificate
will not have a human readable name.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl19.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Open the Security tab in the Profile Editor, and generate the client key.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl20.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>If all is set up correctly, you should see this message. It means Firefox has the private key,
and has obtained a new certificate from the server.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl21.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Refresh the Security tab by clicking on same tab.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl22.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Select automatic login option, and save.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl23.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>Log out from ODS and refresh browser to simulate opening the ODS site. The browser will
ask for a certificate; select the one generated in the steps above.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl24.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>ODS presents your card, and asks to login with certificate. Confirm it.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl25.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
<li>You should now be logged in to ODS via WebID Protocol.
<table class="figure" border="0" cellpadding="0" cellspacing="0">
<tr>
<td>
<img alt="Setting-Up issuer CA" src="../images/ui/foafssl26.png" />
</td>
</tr>
<tr>
<td>Figure: 15.3.9.1. Setting-Up issuer CA</td>
</tr>
</table>
</li>
</ol>
<br />
<a name="vfoafsslsethttpsfoafsll" />
<h3>15.3.10. WebID Protocol ODBC Login</h3>
<p>See details and examples <a href="odbcimplementation.html#secureodbcx509foafsll">here</a>.</p>
<br />
<table border="0" width="90%" id="navbarbottom">
<tr>
<td align="left" width="33%">
<a href="wsdl.html" title="WSDL">Previous</a>
<br />WSDL</td>
<td align="center" width="34%">
<a href="webservices.html">Chapter Contents</a>
</td>
<td align="right" width="33%">
<a href="voauth.html" title="OAuth Support">Next</a>
<br />OAuth Support</td>
</tr>
</table>
</div>
<div id="footer">
<div>Copyright© 1999 - 2009 OpenLink Software All rights reserved.</div>
<div id="validation">
<a href="http://validator.w3.org/check/referer">
<img src="http://www.w3.org/Icons/valid-xhtml10" alt="Valid XHTML 1.0!" height="31" width="88" />
</a>
<a href="http://jigsaw.w3.org/css-validator/">
<img src="http://jigsaw.w3.org/css-validator/images/vcss" alt="Valid CSS!" height="31" width="88" />
</a>
</div>
</div>
</body>
</html>
distrib
>
Fedora
>
14
>
x86_64
>
media
>
updates
>
by-pkgid
>
71d40963b505df4524269198e237b3e3
>
files
>
972
