[geeklog-cvs] Auth_Enterprise/Server README.txt,1.1.1.1,1.2

[tony at iowaoutdoors.org]

Update of /var/cvs/Auth_Enterprise/Server
In directory www:/tmp/cvs-serv26473

Modified Files:
	README.txt 
Log Message:
Starting filling in the blanks a bit.  Some stuff I added is a bit premature but we'll get it done.

Index: README.txt
===================================================================
RCS file: /var/cvs/Auth_Enterprise/Server/README.txt,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** README.txt	15 Jun 2004 15:19:27 -0000	1.1.1.1
--- README.txt	16 Jun 2004 05:23:46 -0000	1.2
***************
*** 2,13 ****
  $Id$
  
  About Auth_Enterprise
  ----------------------
  
  Auth_Enterprise Installation
  -----------------------------
  
! Installation Problems
! ----------------------
  1) For MySQL server, Auth_Enterprise attempts to create all tables with the INNODB type, however,
     if INNODB is not installed or configured they will show up as MyISAM.  To check which table you
--- 2,43 ----
  $Id$
  
+ CONTENTS
+ --------
+ - About Auth_Enterprise
+ - Installing Auth_Enterprise
+ - Common Installation Problems
+ - Support
+ 
  About Auth_Enterprise
  ----------------------
+ Auth_Enterprise was built to provide a solution to any enterprise for managing authentication and
+ authorization.  My many years in the IT field became frustrating when I got tired of each
+ application I was involved with managing user accounts and access rights all in different ways.
+ Worse yet, applications deployed within the enterprise all require seperate sets of credentials
+ making it tough for users to manage.  On another level, Auth_Enterprise attempts to tackle other
+ related issues such as account creation, password recovery and more advanced things like single
+ sign-on.
+ 
+ What makes Auth_Enterprise an enterprise solution is the fact it can support applications written
+ in any language and, in fact, this distribution ships with clients for PHP5, PHP4, Java and C#.
+ Because the core of this system is open source, it is easy for those wishing to port the client
+ to other languages beause the client is truly a thin layer.  Another enterprise feature worth
+ noting is Auth_Enterprise applications can communicate with the server over differnt protocols.
+ Right now XMLRPC and SOAP are supported and the architecture is such that the server (and client)
+ can be expanded to talk over other protocols.
+ 
+ Finally, the true power of Auth_Enterprise is it's ability to authenticate against a variety of
+ datastores.  By default we support PEAR::DB supported databse, LDAP or Active Directory.  Custom
+ providers can be easily added.
+ 
+ One final note is that Auth_Enterprise allows applications to do authentication, authorization or
+ both.  I mention this because it may be easier for some to simply start with the authentication
+ features and worry about adding authorization later.  
  
  Auth_Enterprise Installation
  -----------------------------
  
! Common Installation Problems
! -----------------------------
  1) For MySQL server, Auth_Enterprise attempts to create all tables with the INNODB type, however,
     if INNODB is not installed or configured they will show up as MyISAM.  To check which table you
***************
*** 20,21 ****
--- 50,59 ----
     stable MySQL RPM's from http://www.mysql.com.  Having INNODB is important as it is required
     if you want Auth_Enterprise to use SQL transactions and it provides FOREIGN KEY constraints.
+    
+ Support
+ -------
+ 
+ Free support for Auth_Enterprise can be sought either on my site, http://www.tonybibbs.com, or
+ via IRC on irc.freenode.net in #geeklog (I'm under the handle IA-Outdoors).  Commercial support
+ is also available at an hourly rate.  Those wanting commercial support can contact me directly
+ via email at tony at geeklog.net.