lemonldap-ng/doc/pages/documentation/1.4/idpcas.html
2013-11-02 21:09:55 +00:00

127 lines
5.6 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"
lang="en" dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title></title>
<!-- metadata -->
<meta name="generator" content="Offline" />
<meta name="version" content="Offline 0.1" />
<!-- style sheet links -->
<link rel="stylesheet" media="all" type="text/css" href="../../../css/all.css" />
<link rel="stylesheet" media="screen" type="text/css" href="../../../css/screen.css" />
<link rel="stylesheet" media="print" type="text/css" href="../../../css/print.css" />
</head>
<body>
<div class="dokuwiki export">
<h1><a name="cas_server" id="cas_server">CAS server</a></h1>
<div class="level1">
</div>
<!-- SECTION "CAS server" [1-26] -->
<h2><a name="presentation" id="presentation">Presentation</a></h2>
<div class="level2">
<p>
<acronym title="LemonLDAP::NG">LL::NG</acronym> can act as an <acronym title="Central Authentication Service">CAS</acronym> server, that can allow to federate <acronym title="LemonLDAP::NG">LL::NG</acronym> with:
</p>
<ul>
<li class="level1"><div class="li"> Another <acronym title="LemonLDAP::NG">LL::NG</acronym> system configured with <a href="../../documentation/1.4/authcas.html" class="wikilink1" title="documentation:1.4:authcas">CAS authentication</a></div>
</li>
<li class="level1"><div class="li"> Any <acronym title="Central Authentication Service">CAS</acronym> consumer</div>
</li>
</ul>
<p>
<acronym title="LemonLDAP::NG">LL::NG</acronym> is compatible with the <acronym title="Central Authentication Service">CAS</acronym> protocol <a href="http://www.jasig.org/cas/protocol" class="urlextern" title="http://www.jasig.org/cas/protocol" rel="nofollow">versions 1.0 and 2.0</a>. This protocol does not define any attributes exchange mechanism, so only authentication is managed.
</p>
</div>
<!-- SECTION "Presentation" [27-424] -->
<h2><a name="configuration" id="configuration">Configuration</a></h2>
<div class="level2">
<p>
In the Manager, go in <code>General Parameters</code> » <code>Issuer modules</code> » <code><acronym title="Central Authentication Service">CAS</acronym></code> and configure:
</p>
<ul>
<li class="level1"><div class="li"> <strong>Activation</strong>: set to <code>On</code>.</div>
</li>
<li class="level1"><div class="li"> <strong>Path</strong>: keep <code>^/cas/</code> unless you have change <a href="../../documentation/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4:configlocation">Apache portal configuration</a> file.</div>
</li>
<li class="level1"><div class="li"> <strong>Use rule</strong>: a rule to allow user to use this module, set to 1 to always allow.</div>
</li>
</ul>
<p>
<p><div class="notetip">
For example, to allow only users with a strong authentication level:
</p>
<pre class="code">
$authenticationLevel &gt; 2
</pre>
<p>
</div></p>
</p>
<p>
<p><div class="noteimportant">
Apache rewrite rules must have been activated in <a href="../../documentation/1.4/configlocation.html#portal" class="wikilink1" title="documentation:1.4:configlocation">Apache portal configuration</a>:
</p>
<pre class="code file apache"> &lt;<span class="kw3">IfModule</span> mod_rewrite.c&gt;
<span class="kw1">RewriteEngine</span> <span class="kw2">On</span>
<span class="kw1">RewriteRule</span> ^/cas/.* /index.pl
&lt;/<span class="kw3">IfModule</span>&gt;</pre>
<p>
</div></p>
</p>
<p>
Then go in <code>Options</code> to define:
</p>
<ul>
<li class="level1"><div class="li"> <strong><acronym title="Central Authentication Service">CAS</acronym> login</strong>: the session key used to fill user login (value will be transmitted to <acronym title="Central Authentication Service">CAS</acronym> clients).</div>
</li>
<li class="level1"><div class="li"> <strong>Access control policy</strong>: define if access control should be done on <acronym title="Central Authentication Service">CAS</acronym> service. Three options:</div>
<ul>
<li class="level2"><div class="li"> <strong>none</strong>: no access control, the server will answer without checking if the user is authorized for the service (this is the default)</div>
</li>
<li class="level2"><div class="li"> <strong>error</strong>: if user has no access, an error is shown on the portal, the user is not redirected to <acronym title="Central Authentication Service">CAS</acronym> service</div>
</li>
<li class="level2"><div class="li"> <strong>faketicket</strong>: if the user has no access, a fake ticket is built, and the user is redirected to <acronym title="Central Authentication Service">CAS</acronym> service. Then <acronym title="Central Authentication Service">CAS</acronym> service has to show a correct error when service ticket validation will fail.</div>
</li>
</ul>
</li>
<li class="level1"><div class="li"> <strong><acronym title="Central Authentication Service">CAS</acronym> session module name and options</strong>: choose a specific module if you do not want to mix <acronym title="Central Authentication Service">CAS</acronym> sessions and normal sessions (see <a href="../../documentation/1.4/samlservice.html#saml_sessions_module_name_and_options" class="wikilink1" title="documentation:1.4:samlservice">why</a>).</div>
</li>
</ul>
<p>
<p><div class="notetip">If <code><acronym title="Central Authentication Service">CAS</acronym> login</code> is not set, it uses <code>General Parameters</code> » <code>Logs</code> » <code>REMOTE_USER</code> data, which is set to <code>uid</code> by default
</div></p>
</p>
</div>
<!-- SECTION "Configuration" [425-] --></div><!-- closes <div class="dokuwiki export">-->