Files
CASA/c_kwallet

/***********************************************************************

 *  File: README

 * 

 *  Copyright (C) 2004 Novell, Inc.

 *

 *  This library is free software; you can redistribute it and/or

 *  modify it under the terms of the GNU General Public

 *  License as published by the Free Software Foundation; either

 *  version 2 of the License, or (at your option) any later version.

 *

 *  This library is distributed in the hope that it will be useful,

 *  but WITHOUT ANY WARRANTY; without even the implied warranty of

 *  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU

 *  Library General Public License for more details.

 *

 *  You should have received a copy of the GNU General Public

 *  License along with this library; if not, write to the Free

 *  Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.

 ***********************************************************************/



INTRODUCTION



The LoginCapture provides a service that exports the credentials used

by the user to login to the desktop to the SecretStore wallet. Once in the

SecretStore wallet, the credentials can be leveraged by desktop applications

to provide a better single sign-on experience to the user.



Please note that the better single sign-on experience will only be realized if

the credentials used to log to the back-end systems match the credentials

used to login to the desktop.



FEATURES



The LoginCapture services are provided by components that are platform dependent.



On Linux, LoginCapture provides its services through the use of a PAM module which

is inserted into the PAM configuration chain of the default Windows Manager during

the installation of the LoginCapture rpm.

 

On Windows2000 and above, LoginCapture provides its services through a Credential Manager.



CONTENTS



linux - This folder contains the Linux PAM module implementation.



windows - This folder contanins the Windows Credential Manager implementation.



package - This folder contains the files necessary to build the software packages

under windows and under linux.



REQUIREMENTS FOR BUILDING THE SOFTWARE PACKAGE ON WINDOWS



  - Install Visual Studio .NET 2003

  - Install Cygwin - See instructions below.



Download and start cygwin install:

Browse to http://sources.redhat.com/cygwin/ 



Click on "Install or update now!" or "Install Cygwin now"



Cygwin Setup:

Next



Cygwin Setup - Choose Installation Type:

Install from Internet

Next



Cygwin Setup - Choose Installation Directory:

Root Directory: C:\cygwin

Install For:  "All Users"



Default Text File Type: DOS



Cygwin Setup - Select Local Package Directory:

  Local Package Directory: C:\cygwin-packages



Cygwin Setup - Select Connection Type:

  Direct Connection



Choose A Download Site:

  ftp://ftp.nas.nasa.gov 



Cywin Setup - Select Packages:

  Base:

    defaults



  Devel:

    autoconf

    automake

    libtool

    make

    pkgconfig

    cvs

    gcc

    gcc-g++



  Editors:

    vim (optional)



  Net:

    openssh

    openssl



  Text:

    more



  Utils:

    clear (optional)



Cygwin Setup - Create Icons:

Finish



Edit cygwin.bat (c:\cygwin\cygwin.bat) to add a call to

%VS71COMNTOOLS%\vsvars32.bat (see example below). This sets up the

Visual Studio tools in Cygwin.



Sample cygwin.bat:



@echo off



call "%VS71COMNTOOLS%\vsvars32.bat" > NUL



C:

chdir C:\cygwin\bin



bash --login -i





REQUIREMENTS FOR BUILDING THE SOFTWARE PACKAGE ON LINUX



Install latest mono and mono-devel RPM - Obtain RPMs from

www.go-mono.org.





BUILDING THE SOFTWARE PACKAGE



Windows:  Start at Step 1.

Linux:  Skip to Step 2.



1. Run cygwin.bat to start up Cygwin.



2. Generate autotools files:

./autogen.sh --prefix=/<install_dir>  [--enable-debug]

(<install_dir> is some writable directory where 'make install' will

install files for testing.



3. To reconfigure later, or to configure software that came from a source

distribution (.tar.gz) file, use configure.

./configure --prefix/<install_dir> [--enable-debug]

(run ./configure --help for more options)



4. Select your make target, here are a few interesting ones:



make [all] - build product files (package files not included)



make clean - clean up files built by 'make all'



make package - build product and package files



make package-clean - clean up package files



make install - install product files to <install_dir> specified by

--prefix during configure



make uninstall - undo 'make install'



make dist - build a source distribution tarball.



make distclean - removes files to return state back to same as the

source distribution (configure, Makefile.in files, and other distributed

autotools files are not removed)



make maintainer-clean - removes files to return state back to same as

the CVS checkout (you will need to run ./autogen.sh again before running

make again)