CASA/auth_token/server/AuthTokenSvc
2006-05-19 20:11:14 +00:00
..
.settings Changing the name of CasaAuthServer to AuthTokenSvc and changing the 2006-05-05 17:35:21 +00:00
sampleConf Adding a folder with a sample configuration for the ATS. 2006-05-18 22:00:11 +00:00
src/com/novell/casa/authtoksvc Added plug-in capability for authentication mechanisms. 2006-05-18 18:55:10 +00:00
WebContent Changed to utilize a single Rpc servlet. 2006-05-16 15:16:34 +00:00
.classpath Changing the name of CasaAuthServer to AuthTokenSvc and changing the 2006-05-05 17:35:21 +00:00
.project Changing the name of CasaAuthServer to AuthTokenSvc and changing the 2006-05-05 17:35:21 +00:00
Makefile.am Added new modules to makefile. 2006-05-18 21:35:58 +00:00
README Documentation updates. 2006-05-19 20:11:14 +00:00
TODO Documentation updates. 2006-05-19 20:11:14 +00:00

/***********************************************************************
 *
 *  README for AuthTokenSvc
 *
 ***********************************************************************/

INTRODUCTION

AuthTokenSvc is the CASA Authentication Token Service (ATS). It is implemented
as a Java servlet and supporting classes that execute in the Tomcat environment.

The ATS is responsible for providing clients with the necessary authentication
policy information, for authenticating client entities, and for providing
clients with Authentication Tokens that they can then use for authenticating
to CASA Authentication enabled services.

The ATS utilizes mechanism plug-ins for authenticating client entities as well
Identity Token Providers for the generation of Identity Tokens.

CONFIGURATION

AuthTokenSvc configuration consists of multiple entities. Most of the AuthTokenSvc
configuration is contained within the "conf" folder under the WEB-INF folder of the
application. For an example configuration setup for the AuthTokenSvc see the
sampleConf folder. 

CONFIGURING AUTHENTICATION MECHANISMS

Authentication mechanisms available to the AuthTokenSvc are configured by creating
a sub-folder named after the authentication mechanism type under the
conf/auth_mechanisms folder. The authentication mechanism folders must contain a
settings file named mechanism.settings. The mechanism.settings file must contain the
name of the class implementing the mechanism along with path information which
can be utilized by the ATS to load the class. The mechanism.settings file can
also contain mechanism specific settings.

The following setting is mandatory: 

One of the following settngs must be included:

For example mechanism.settings files look at sampleConf/auth_mechanisms/ 



CONFIGURING ADDITIONAL IDENTITY TOKEN PROVIDERS

- TBD -

SECURITY CONSIDERATIONS

- TBD -