 
About Authentication Service data instances
|
<img src=
"../../../navdropup.gif" alt="SysAdmin category" " border="0" class="inline" /></a>
</td>
</tr>
</table>
<div class="INNER">
<table border="0">
<tr>
<td style="text-align:center" width="65"><a href=
"new.htm">New</a></td>
<td style="text-align:center" width="65"><a class="bfield" href=
"service.htm">Service</a></td>
<td style="text-align:center" width="80"><a class="bfield" href=
"mapping.htm">Mapping</a></td>
<td style="text-align:center" width="80"><a class="bfield" href=
"custom.htm">Custom</a></td>
<td style="text-align:center" width="65"><a class="bfield" href=
"../../../basics/v6portal/v6completingrdatahistory.htm">
History</a></td>
<td style="text-align:center" width="65"><a href=
"related.htm">More...</a></td>
</tr>
</table>
<h3 class="ref">Purpose</h3>
<p><tt>C-527 03-04</tt> The Authentication Service feature enables you to
override the default authentication process. Use an authentication
service when you want to configure Process Commander to do one of the
following:</p>
<ul>
<li>Use a Lightweight Directory Access Protocol (LDAP)-compliant
directory server to authenticate the Process Commander users.</li>
<li>Use some other vendor-specific security solution to authenticate
the Process Commander users.</li>
<li>Implement single sign-on.</li>
</ul>
<p>Complete two main steps when using this feature:</p>
<ol>
<li>Create an authentication service data instance that identifies
activities that override the default Process Commander authentication
process. If your goal is to configure Process Commander to use an
LDAP-compliant directory server to authenticate users, use the
Authentication accelerator. See <a href=
"../../../tools/authenticationwizard/aboutauthenticationwizard.htm">About
the Authentication accelerator</a>.</li>
<li>Insert a servlet definition element and a servlet-mapping element
in the Process Commander <code>web.xml</code> file that identifies the
name of the authentication service.</li>
</ol>
<p>When initially installed, the <code>web.xml</code> file contains three
servlet definitions you can use for authentication service
implementations: <code>WebLDAP1</code> to <code>WebLDAP3</code>. By
choosing an authentication service name that matches one of these, you
can implement up to three without changing the <code>web.xml</code> file
and without redeploying Process Commander.</p>
<p>For information about configuring and using authentication services,
see <i><img src="../../../shared/pdn.gif" alt="PDN" width="16" height=
"16" class="inline" />Authentication in PegaRULES Process Commander</i>,
a document available from the Integration area of the Pega Developer
Network.</p>
<h3 class="ref">Category</h3>
<p>Authentication services are instances of the
<cite>Data-Admin-AuthService</cite> class. They belong to the SysAdmin
category.</p>
<table width="100%" border="0" class="tablegray">
<tr valign="top">
<td width="3%"><img src="../../../shared/standardrule.gif" alt=
"Initial data instances" width="13" height="16" /></td>
<td><a href=
"../../../zstandarddata/data-admin-authservice.htm">Atlas —
Initial Authentication Service data instances</a></td>
</tr>
</table>
<p><a class="small" href=
"../../../category/sysadmincategory.htm"><img src=
"../../../sharedv6/v6Icons/RuleCategories/SysAdmin.png" width="12" height="12" align="texttop" class="inline" />SysAdmin category</a><br />
<a class="small" href="../../../home.htm"><img src=
"../../../helphome.gif" alt="Help System home page" width="17" height=
"15" class="inline" />Help Home</a></p>
</div>
</body>
</html>
|