geos_one/CASA
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Documentation update for cypress release

Browse Source
This commit is contained in:
Jim Norman 2007-09-24 18:18:11 +00:00
parent 041aecf2c8
commit 5d3aab0135
20 changed files with 791 additions and 1134 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

522
CASA/doc/product/Readme.txt
View File

@ -1,503 +1,173 @@
Common Authentication Service Adapter (CASA)
September 28, 2007
1.0 Overview
2.0 Documentation
3.0 Known Issues
4.0 Legal Notices
1.0 Overview
Common Authentication Service Adapter (CASA) provides
a common infrastructure for client authentication
across the Linux* and Microsoft* Windows* desktops.
Novell products (such as GroupWise, GroupWise
Messenger, iPrint, Novell iFolder, and the Novell
clients for Windows and Linux) are integrated with the
miCASA interface and can take advantage of the
credential store that provides the cornerstone for
CASA.
The main components of CASA on Linux are:
- CASA Identity Development Kit (IDK): The IDK
provides a set of APIs that application and service
developers can use to write user/application
credentials to the credential store. The IDK APIs
internally store the credentials passed onto them
by the applications in miCASAd. There are C, C++,
C# and Java bindings available for the CASA IDK.
- miCASAd: An active component that starts during
boot time. On Linux, miCASAd is available in the
run-levels 1, 2, 3 and 5. It runs with root
privileges and is active as long as the system is
up. It stores and provides credentials or secrets
based on the Linux user identifier (uid) of the
process that makes the IDK API calls. The
credentials, which are stored by applications in
miCASAd, are maintained in memory and written to
disk for this release. Session-based secrets implies
secrets that are stored in an in-memory cache, are
available only as long as the user is in session on
the desktop, and are destroyed when miCASA daemon
is restarted or the user logs off. When the user
logs back in, the secrets written to disk are read
back into memory.
- Login Credential Capture Module: On Linux, the
login credential capture module is implemented as a
PAM module. This PAM module captures the user's
desktop login credentials and stores them in
miCASAd using the IDK APIs. This PAM module is
placed as the last module in the auth and session
stacks of xdm, gdm, kdm, login and sshd PAM
configuration files. The functionality of this
module is to store the credentials in miCASAd.
Any PAM module that uses the IDK APIs must set its
effective user id temporarily to that of the user
logging in (the user returned by calling
pam_get_user()), if the credentials need to be
stored against that user. There might be cases
where the user obtained through pam_get_user()
might not be the one against whom the PAM module
actually intends to store credentials.
2.0 Documentation
To read or print the documentation, you need Adobe
Acrobat Reader 4.0
(http://www.adobe.com/prodindex/acrobat/readstep.html)
.
The document in this download was created as a
standalone file; therefore, links to files in other
downloads will not resolve.
The download includes a single file:
CASA_Reference_Guide.pdf in the [install directory]\doc
directory.
3.0 Known issues
- Secrets with IDs using reserved characters may fail.
These will be fixed in a future release. Reserved
characters are
:
\
- CASA Manager might report an error stating that
miCASA Services are not available when selecting
the 'File' option on the main menu. This problem
is resolved by upgrading mono to the latest version
(1.1.9 or later) available for download at
http://www.mono-project.com/Downloads.
- CASA install rpm that is intended for 32 bit architecture
should not be installed on 64 bit architecture because
it can cause runtime problems.
- Since CASA is tied to the Linux login process via PAM,
events that cause the system to become inconsistent or
unstable may cause a user to be unable to login to the
workstation. Some possible causes of inconsistency or
instability are:
- Installing 32 bit CASA RPMs on a 64 bit OS
- Performing a hard reset on the machine
Following the steps below will restore the ability to
login.
1) Reboot machine
2) When boot loader menu appears, type "init=/bin/bash"
(without quotes) on the options line and then Enter.
This will cause the machine to boot into a command
shell with root privileges.
3) At the command prompt type "chkconfig micasad off"
(without quotes). This will prevent the CASA daemon
from being loaded during bootup.
4) With a console based text editor (i.e. vi, emacs)
remove all lines referencing the pam_micasa module in
the following pam configuration files (some files may
not exist depending on what desktop managers have
been installed:
- /etc/pam.d/gdm
- /etc/pam.d/xdm
- /etc/pam.d/kdm
- /etc/pam.d/sshd
- /etc/pam.d/login
5) At the command prompt type "init 5" (without quotes)
to boot into runlevel 5. This will provide you with a
graphical login prompt. You should be able to login
at this point.
After you have restored login capabilities, you will need
to resolve the inconsistency that prevented login in the
first place. If you had installed a 32 bit CASA package
on a 64 bit OS, you will need to uninstall the 32 bit
package and install a CASA package built for 64 bit
architectures. If you are recovering from a hard reset
no further action should be needed.
To make it so CASA will run at boot time, open a shell and
at the prompt type "chkconfig micasad 1235" (without
quotes). This will cause micasad to be run at runlevels
1, 2, 3, and 5.
- When logged in to a KDE session, the gnome-keyring-daemon
does not run by default. Therefore, all apps that access
the daemon, including our CASAManager will not be able to
manage/access the gnome-keyring.
You can manually start the daemon by running the following
command from a shell prompt:
gnome-keyring-daemon
When the gnome-keyring-daemon starts, it prints the
GNOME_KEYRING_SOCKET environment variable and its value to
the terminal. In Gnome, the daemon is started and the
environment variable is loaded into your X session
environment by default, but in KDE, you will
have to manually load it.
To load this environment variable, run a command similar to
the following command from a shell prompt (replacing the
value of the environment variable with what the daemon
output to the screen when you started it):
export GNOME_KEYRING_SOCKET=/tmp/keyring-oaTsPs/socket
Then you can run CASAManager GUI (from the same terminal
you exported the variable from) and you will be able to
manage and use the gnome-keyring in KDE just like you
could if you were logged into Gnome.
4.0 Legal Notices
Novell, Inc. makes no representations or warranties
with respect to the contents or use of this
documentation, and specifically disclaims any express
or implied warranties of merchantability or fitness
for any particular purpose. Further, Novell, Inc.
reserves the right to revise this publication and to
make changes to its content, at any time, without
obligation to notify any person or entity of such
revisions or changes.
Further, Novell, Inc. makes no representations or
warranties with respect to any software, and
specifically disclaims any express or implied
warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the
right to make changes to any and all parts of Novell
software, at any time, without any obligation to
notify any person or entity of such changes.
You may not use, export, or re-export this product in
violation of any applicable laws or regulations
including, without limitation, U.S. export regulations
or the laws of the country in which you reside.
Copyright 2005 Novell, Inc. All rights reserved.
Permission is granted to copy, distribute, and/or
modify this document under the terms of the GNU Free
Documentation License (GFDL), Version 1.2 or any later
version, published by the Free Software Foundation
with no Invariant Sections, no Front-Cover Texts, and
no Back-Cover Texts. A copy of the GFDL can be found
at http://www.fsf.org/licenses/fdl.html.
THIS DOCUMENT AND MODIFIED VERSIONS OF THIS DOCUMENT
ARE PROVIDED UNDER THE TERMS OF THE GNU FREE
DOCUMENTATION LICENSE WITH THE FURTHER UNDERSTANDING
THAT:
1. THE DOCUMENT IS PROVIDED ON AN "AS IS" BASIS,
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES
THAT THE DOCUMENT OR MODIFIED VERSION OF THE DOCUMENT
IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR
PURPOSE, OR NON-INFRINGING. THE ENTIRE RISK AS TO THE
QUALITY, ACCURACY, AND PERFORMANCE OF THE DOCUMENT OR
MODIFIED VERSION OF THE DOCUMENT IS WITH YOU. SHOULD
ANY DOCUMENT OR MODIFIED VERSION PROVE DEFECTIVE IN
ANY RESPECT, YOU (NOT THE INITIAL WRITER, AUTHOR OR
ANY CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY
SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF
WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS
LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED VERSION OF
THE DOCUMENT IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS
DISCLAIMER; AND
* Section 1, “Overview”
* Section 2, “Documentation"
* Section 3, “Documentation Conventions"
* Section 4, “Known Issues"
* Section 5, “Open Source Code"
* Section 6, “Legal Notices"
2. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY,
WHETHER IN TORT (INCLUDING NEGLIGENCE), CONTRACT, OR
OTHERWISE, SHALL THE AUTHOR, INITIAL WRITER, ANY
CONTRIBUTOR, OR ANY DISTRIBUTOR OF THE DOCUMENT OR
MODIFIED VERSION OF THE DOCUMENT, OR ANY SUPPLIER OF
ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING,
WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK
STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND
ALL OTHER DAMAGES OR LOSSES ARISING OUT OF OR RELATING
TO USE OF THE DOCUMENT AND MODIFIED VERSIONS OF THE
DOCUMENT, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED
OF THE POSSIBILITY OF SUCH DAMAGES.
1 Overview
Common Authentication Service Adapter (CASA) provides a common infrastructure for client authentication across the Linux* and Microsoft* Windows* desktops. Novell® products (such as GroupWise®, GroupWise Messenger, iPrint, Novell iFolder®, and the Novell clients for Windows and Linux) are integrated with the miCASA interface and can take advantage of the credential store that provides the cornerstone for CASA.
Novell, Inc. has intellectual property rights relating
to technology embodied in the product that is
described in this document. In particular, and without
limitation, these intellectual property rights may
include one or more of the U.S. patents listed at
http://www.novell.com/company/legal/patents/ and one
or more additional patents or pending patent
applications in the U.S. and in other countries.
CASA provides the following main components:
* CASA Identity Development Kit (IDK): The developer kit provides a set of APIs that application and service developers can use to write user/application credentials to the credential store. The APIs internally store the credentials passed onto them by the applications in miCASAd. There are C, C++, C# and Java bindings available for the CASA Identity Development Kit (IDK).
AppNotes is a registered trademark of Novell, Inc.
* Login Credential Capture Module: On Linux, the login credential capture module is implemented as a PAM module. This PAM module captures the user’s desktop login credentials and stores them in miCASAd using the IDK APIs. This PAM module is placed as the last module in the auth and session stacks of xdm, gdm, kdm, login and sshd PAM configuration files. In the auth stack, the functionality of this module is to store the credentials in miCASAd and in the session stack, then closes the user’s session with miCASAd.
AppTester is a registered trademark of Novell, Inc. in
the United States.
* miCASAd: An active component that starts during boot time.
ASM is a trademark of Novell, Inc.
Linux:
BorderManager is a registered trademark of Novell,
Inc.
miCASAd stores and provides credentials or secrets based on the user identifier (uid) of the process that makes the IDK API calls. It is available in the run-levels 1, 2, 3 and 5. It runs with root privileges and is active as long as the system is up.
BrainShare is a registered service mark of Novell,
Inc. in the United States and other countries.
Windows:
C3PO is a trademark of Novell, Inc.
CASA consists of a single CASA.msi, which is the installation module that contains the following components that match their Linux counterparts:
Certified Novell Engineer is a service mark of Novell,
Inc.
* CASA-gui.msm
Client32 is a trademark of Novell, Inc.
* CASA.msm
CNE is a registered service mark of Novell, Inc.
A separate Windows package called CASA-devel.msi installs the CASA development kit.
ConsoleOne is a registered trademark of Novell, Inc.
Credentials saved by user applications are encrypted and saved to the file system. When the user logs into the desktop, the credentials are read back into computer memory and made available to user applications.
Controlled Access Printer is a trademark of Novell,
Inc.
NOTE: Any pluggable authentication module (PAM) that uses the IDK APIs must set its effective user ID temporarily to that of the user logging in (the user returned by calling pam_get_user()), if the credentials need to be stored against that user. There might be cases where the user obtained through pam_get_user() might not be the one against whom the PAM module actually intends to store credentials.
Custom 3rd-Party Object is a trademark of Novell, Inc.
2 Documentation
DeveloperNet is a registered trademark of Novell, Inc.
in the United States and other countries.
The following sources provide information about CASA:
DirXML is a registered trademark of Novell, Inc.
* Product documentation included with the software: The download includes a single file: CASA Administration Guide(casa_enu.pdf) in the [install directory]\doc directory.
eDirectory is a trademark of Novell, Inc.
* Novell CASA online product documentation: Common Authentication Service Adapter (http://developer.novell.com/wiki/index.php/Casa)
Excelerator is a trademark of Novell, Inc.
* Bandit Open Source Common Authentication Services Adapter (CASA) Documentation (http://www.bandit-project.org/index.php/Common_Authentication_Services_Adapter_%28CASA%29_Documentation)
exteNd is a trademark of Novell, Inc.
To read or print the documentation, you need Adobe Acrobat Reader 4.0 (http://www.adobe.com/prodindex/acrobat/readstep.html).
exteNd Director is a trademark of Novell, Inc.
The document in this download was created as a standalone file; therefore, links to files in other downloads will not resolve.
exteNd Workbench is a trademark of Novell, Inc.
3 Documentation Conventions
FAN-OUT FAILOVER is a trademark of Novell, Inc.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
GroupWise is a registered trademark of Novell, Inc. in
the United States and other countries.
A trademark symbol (® , TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Hardware Specific Module is a trademark of Novell,
Inc.
4 Known Issues
Hot Fix is a trademark of Novell, Inc.
Here are some known issues when deploying CASA 1.7:
* Section 4.1, “Secret ID Failure"
* Section 4.2, “Upgrading the CASA Authentication Service"
* Section 4.3, “Runtime Architecture Compatibility"
* Section 4.4, “Unstable Login Conditions"
* Section 4.5, “Manually Starting the Gnome Keyring"
* Section 4.6, “Installing CASA Developer Packages"
iChain is a registered trademark of Novell, Inc.
4.1 Secret ID Failure
Internetwork Packet Exchange is a trademark of Novell,
Inc.
Secrets with IDs using \ as a reserved character might fail. This will be fixed in a future release.
IPX is a trademark of Novell, Inc.
4.2 Upgrading the CASA Authentication Service
IPX/SPX is a trademark of Novell, Inc.
There is a know problem with upgrading the CASA authentication service (ATS) to a later release.
If you upgrade manually, you must first stop the CASA ATS before applying the upgrade. You do this by issuing the following command: /etc/init.d/casa_atsd stop
jBroker is a trademark of Novell, Inc.
You may then proceed with the upgrade.
Link Support Layer is a trademark of Novell, Inc.
If the upgrade occurs as part of an automated update, then the CASA ATS must be restarted using the following procedure:
LSL is a trademark of Novell, Inc.
1 Find the CASA ATS process that needs to be killed by entering the following comand: ps -ef | grep casaats
ManageWise is a registered trademark of Novell, Inc.,
in the United States and other countries.
2 Kill the listed ATS process.
Mirrored Server Link is a trademark of Novell, Inc.
3 Restart the CASA ATS by entering the following command: /etc/init.d/casa_atsd start
Mono is a registered trademark of Novell, Inc.
4.3 Runtime Architecture Compatibility
MSL is a trademark of Novell, Inc.
To avoid runtime problems, do not install CASA 32 bit architecture RPMs intended for 64 bit architecture machines.
My World is a registered trademark of Novell, Inc. in
the United States.
4.4 Unstable Login Conditions
NCP is a trademark of Novell, Inc.
Because CASA is tied to the Linux login process via a PAM, events that cause the system to become inconsistent or unstable might prevent users from logging in to workstations. Some possible causes of inconsistency or instability are:
NDPS is a registered trademark of Novell, Inc.
* Installing 32 bit CASA RPMs on a 64 bit OS
NDS is a registered trademark of Novell, Inc. in the
United States and other countries.
* Performing a hard reset on the machine
NDS Manager is a trademark of Novell, Inc.
Use the following steps to restore the ability to login:
NE2000 is a trademark of Novell, Inc.
1 Reboot the machine.
NetMail is a registered trademark of Novell, Inc.
2 When boot loader menu appears, execute init=/bin/bash on the command option line. This causes the machine to boot into a command shell with root privileges.
NetWare is a registered trademark of Novell, Inc. in
the United States and other countries.
3 To prevent the CASA daemon from loading during bootup, enter the following at the command prompt:
chkconfig micasad off
NetWare/IP is a trademark of Novell, Inc.
4 With a console-based text editor (e.g., Vi, Emacs), remove all lines referencing the pam_micasa module in the following PAM configuration files (some files may not exist, depending on which desktop managers are installed):
* /etc/pam.d/gdm
* /etc/pam.d/xdm
* /etc/pam.d/kdm
* /etc/pam.d/sshd
* /etc/pam.d/login
NetWare Core Protocol is a trademark of Novell, Inc.
5 At the command prompt execute init 5 to boot into runlevel 5 to obtain a graphical login prompt. You should be able to login at this point.
NetWare Loadable Module is a trademark of Novell, Inc.
6 To enable CASA to run at boot time, open a shell and at the prompt type
chkconfig micasad 1235. This causes micasad to run at runlevels 1, 2, 3, and 5.
NetWare Management Portal is a trademark of Novell,
Inc.
7 After you have restored login capabilities, resolve the inconsistency that prevented the initial login. If you had installed a 32 bit CASA package on a 64 bit OS, uninstall the 32 bit package and install a CASA package built for 64 bit architectures. If you are recovering from a hard reset, no further action should be needed.
NetWare Name Service is a trademark of Novell, Inc.
4.5 Manually Starting the Gnome Keyring
NetWare Peripheral Architecture is a trademark of
Novell, Inc.
When logged in to a KDE session, the gnome-keyring-daemon does not run by default. Therefore, all applications that access the daemon, including the CASAManager, will not be able to access or manage the gnome-keyring.
NetWare Requester is a trademark of Novell, Inc.
You can manually start the daemon by running the following command from a shell prompt: gnome-keyring-daemon
NetWare SFT and NetWare SFT III are trademarks of
Novell, Inc.
After the gnome-keyring-daemon starts, it prints the GNOME_KEYRING_SOCKET environment variable and its value to the terminal. In Gnome, the daemon starts and the environment variable loads into your X session environment by default. However, in KDE, you must manually load this environment variable:
NetWare SQL is a trademark of Novell, Inc.
1 Run a command similar to the following command from a shell prompt (replacing the value of the environment variable with what the daemon output to the screen when you started it): export GNOME_KEYRING_SOCKET=/tmp/keyring-oaTsPs/socket
NetWire is a registered service mark of Novell, Inc.
in the United States and other countries.
2 Run the CASAManager GUI (from the same terminal you exported the variable from).
You can now manage and use the gnome-keyring in KDE just like you could if you were logged into Gnome.
NLM is a trademark of Novell, Inc.
4.6 Installing CASA Developer Packages
NMAS is a trademark of Novell, Inc.
CASA-devel packages are available only for software development and are not automatically included when installing a production Novell Open Enterprise Server. Developers should install CASA-devel at the same time Auth-token-server-devel and Auth-token-client-devel are installed. CASA is an Open Source project found at http://forge.novell.com/modules/xfmod/project/?casa. Download CASA-devel from there.
NMS is a trademark of Novell, Inc.
4.7 Using CASA in chroot Environment
Novell is a registered trademark of Novell, Inc. in
the United States and other countries.
For an application to access CASA in a change root (chroot) environment, the root user must do the following:
Novell Application Launcher is a trademark of Novell,
Inc.
1 Copy the micasa libraries to the chroot directory, as shown in the following example: cp /usr/lib/libmicasa* <chrootdir>/usr/lib/
Novell Authorized Service Center is a service mark of
Novell, Inc.
2 Create the CASA socket file in the chroot directory by linking the current CASA socket. An example of how to do this is explained below:
Novell Certificate Server is a trademark of Novell,
Inc.
2a From the <chrootdir>/var/run directory, execute the following command: ln /var/run/.novellCASA
Novell Client is a trademark of Novell, Inc.
NOTE: The chrootdir must be on the same disk partition as /var/run.
Novell Cluster Services is a trademark of Novell, Inc.
5 Open Source Code
Novell Directory Services is a registered trademark of
Novell, Inc.
Novell, hereby, offers to give any third party a complete machine-readable copy of the source code of Common Authentication Service Adapter (CASA) under the terms of Sections 1 and 2 of version 2 of the GNU General Public License as published by the Free Software Foundation, on a medium customarily used for software interchange. Please contact Novell Developer Services if you require a copy of the same.
Novell Distributed Print Services is a trademark of
Novell, Inc.
6 Legal Notices
Novell iFolder is a registered trademark of Novell,
Inc.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Novell Labs is a trademark of Novell, Inc.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Novell SecretStore is a registered trademark of
Novell, Inc.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Novell Security Attributes is a trademark of Novell,
Inc.
Novell Storage Services is a trademark of Novell, Inc.
Novell, Yes, Tested & Approved logo is a trademark of
Novell, Inc.
Nsure is a registered trademark of Novell, Inc.
Nterprise is a trademark of Novell, Inc.
Nterprise Branch Office is a trademark of Novell, Inc.
ODI is a trademark of Novell, Inc.
Open Data-Link Interface is a trademark of Novell,
Inc.
Packet Burst is a trademark of Novell, Inc.
PartnerNet is a registered service mark of Novell,
Inc. in the United States and other countries.
Printer Agent is a trademark of Novell, Inc.
QuickFinder is a trademark of Novell, Inc.
Red Box is a trademark of Novell, Inc.
Red Carpet is a registered trademark of Novell, Inc.
in the United States and other countries.
Sequenced Packet Exchange is a trademark of Novell,
Inc.
SFT and SFT III are trademarks of Novell, Inc.
SPX is a trademark of Novell, Inc.
Storage Management Services is a trademark of Novell,
Inc.
SUSE is a registered trademark of SUSE AG, a Novell
business.
System V is a trademark of Novell, Inc.
Topology Specific Module is a trademark of Novell,
Inc.
Transaction Tracking System is a trademark of Novell,
Inc.
TSM is a trademark of Novell, Inc.
TTS is a trademark of Novell, Inc.
Universal Component System is a registered trademark
of Novell, Inc.
Virtual Loadable Module is a trademark of Novell, Inc.
VLM is a trademark of Novell, Inc.
Yes Certified is a trademark of Novell, Inc.
ZENworks is a registered trademark of Novell, Inc. in
the United States and other countries.
All third-party trademarks are the property of their
respective owners.
Copyright © 2007 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/trademarks/tmlist.html).
All third-party trademarks are the property of their respective owners.

BIN
CASA/doc/product/casa_enu.pdf
View File

Binary file not shown.

140
CASA/extern/w32/namedpipes/AppModule.InterProcessComm/AppModule.InterProcessComm.xml vendored
View File

@ -4,87 +4,33 @@
<name>AppModule.InterProcessComm</name>
</assembly>
<members>
<member name="T:AppModule.InterProcessComm.IChannelManager">
<summary>
Interface, which defines methods for a Channel Manager class.
</summary>
<remarks>
A Channel Manager is responsible for creating and maintaining channels for inter-process communication. The opened channels are meant to be reusable for performance optimization. Each channel needs to procees requests by calling the <see cref="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">HandleRequest</see> method of the Channel Manager.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Initialize">
<summary>
Initializes the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Stop">
<summary>
Closes all opened channels and stops the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">
<summary>
Handles a request.
</summary>
<remarks>
This method currently caters for text based requests. XML strings can be used in case complex request structures are needed.
</remarks>
<param name="request">The incoming request.</param>
<returns>The resulting response.</returns>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.WakeUp">
<summary>
Forces the Channel Manager to exit a sleeping mode and create a new channel.
</summary>
<remarks>
Normally the Channel Manager will create a number of reusable channels, which will handle the incoming reqiests, and go into a sleeping mode. However if the request load is high, the Channel Manager needs to be asked to create additional channels.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.RemoveServerChannel(System.Object)">
<summary>
Removes an existing channel.
</summary>
<param name="param">A parameter identifying the channel.</param>
</member>
<member name="P:AppModule.InterProcessComm.IChannelManager.Listen">
<summary>
Indicates whether the Channel Manager is in listening mode.
</summary>
<remarks>
This property is left public so that other classes, like a server channel can start or stop listening based on the Channel Manager mode.
</remarks>
</member>
<member name="T:AppModule.InterProcessComm.IClientChannel">
<member name="T:AppModule.InterProcessComm.InterProcessIOException">
<summary>
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.String)">
<member name="F:AppModule.InterProcessComm.InterProcessIOException.IsServerAvailable">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.IO.Stream)">
<member name="F:AppModule.InterProcessComm.InterProcessIOException.ErrorCode">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.Object)">
<member name="M:AppModule.InterProcessComm.InterProcessIOException.#ctor(System.String)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
<param name="text"></param>
</member>
<member name="M:AppModule.InterProcessComm.IClientChannel.Create">
<member name="M:AppModule.InterProcessComm.InterProcessIOException.#ctor(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
<summary>
</summary>
<returns></returns>
<param name="info"></param>
<param name="context"></param>
</member>
<member name="T:AppModule.InterProcessComm.IInterProcessConnection">
<summary>
@ -231,33 +177,87 @@
</summary>
</member>
<member name="T:AppModule.InterProcessComm.InterProcessIOException">
<member name="T:AppModule.InterProcessComm.IChannelManager">
<summary>
Interface, which defines methods for a Channel Manager class.
</summary>
<remarks>
A Channel Manager is responsible for creating and maintaining channels for inter-process communication. The opened channels are meant to be reusable for performance optimization. Each channel needs to procees requests by calling the <see cref="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">HandleRequest</see> method of the Channel Manager.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Initialize">
<summary>
Initializes the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.Stop">
<summary>
Closes all opened channels and stops the Channel Manager.
</summary>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.HandleRequest(System.String)">
<summary>
Handles a request.
</summary>
<remarks>
This method currently caters for text based requests. XML strings can be used in case complex request structures are needed.
</remarks>
<param name="request">The incoming request.</param>
<returns>The resulting response.</returns>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.WakeUp">
<summary>
Forces the Channel Manager to exit a sleeping mode and create a new channel.
</summary>
<remarks>
Normally the Channel Manager will create a number of reusable channels, which will handle the incoming reqiests, and go into a sleeping mode. However if the request load is high, the Channel Manager needs to be asked to create additional channels.
</remarks>
</member>
<member name="M:AppModule.InterProcessComm.IChannelManager.RemoveServerChannel(System.Object)">
<summary>
Removes an existing channel.
</summary>
<param name="param">A parameter identifying the channel.</param>
</member>
<member name="P:AppModule.InterProcessComm.IChannelManager.Listen">
<summary>
Indicates whether the Channel Manager is in listening mode.
</summary>
<remarks>
This property is left public so that other classes, like a server channel can start or stop listening based on the Channel Manager mode.
</remarks>
</member>
<member name="T:AppModule.InterProcessComm.IClientChannel">
<summary>
</summary>
</member>
<member name="F:AppModule.InterProcessComm.InterProcessIOException.IsServerAvailable">
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.String)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="F:AppModule.InterProcessComm.InterProcessIOException.ErrorCode">
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.IO.Stream)">
<summary>
</summary>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.InterProcessIOException.#ctor(System.String)">
<member name="M:AppModule.InterProcessComm.IClientChannel.HandleRequest(System.Object)">
<summary>
</summary>
<param name="text"></param>
<param name="request"></param>
<returns></returns>
</member>
<member name="M:AppModule.InterProcessComm.InterProcessIOException.#ctor(System.Runtime.Serialization.SerializationInfo,System.Runtime.Serialization.StreamingContext)">
<member name="M:AppModule.InterProcessComm.IClientChannel.Create">
<summary>
</summary>
<param name="info"></param>
<param name="context"></param>
<returns></returns>
</member>
</members>
</doc>

960
CASA/extern/w32/namedpipes/AppModule.NamedPipes/AppModule.NamedPipes.xml vendored
View File

File diff suppressed because it is too large Load Diff

43
CASA/gui/help/en/AddNewSecrets.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,9 +16,11 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Adding New Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">CASA enables you to manually create new secrets or to
manage secrets that have been previously created by programs that integrate
@ -27,37 +29,38 @@
<li>In CASA Manager, click File &gt; New &gt; New Secret.</li>
<li>Type the identifying name of the new secret in the Secret ID field, such
as, Example Secret.</li>
<li>Type the name of the key and its value in the Key and Value fields,
such as, Key: Password, and Value: testpassword.
The asterisk (*) is the only restricted character in both the Key and Value fields.</li>
<li>Click the + button to add the newly formed Key-Value pair for the
new secret. </li>
<li>By default, to safeguard secrets, values are shown as asterisks (*).
To show values in clear text, select Show Values in Clear Text and
enter your master password to enable a single instance display
of the value in the Value field.</li>
<li>Type the name of the key and its value in the Key and Value fields:</li>
<ul>
<li><b>Key:</b> Password
<li><b>Value:</b> testpassword
</li>
</ul>
<li>Click the + button to add the newly formed key-value pair for the new
secret. </li>
<li>By default, to safeguard secrets, values are shown as asterisks (*). To
show values in clear text, select <i>Show Values in Clear Text</i> and enter your
master password to enable a single instance display of the value in the
Value field.</li>
<li>Click OK to add the new secret, with its corresponding Key-Value pair,
to the credential store. The secret will now display in the Secret-ID window,
indicating that it has been added to the miCASA credential store.</li>
</ol>
<p>See also <a href="EditingSecrets.html" target="_parent">Editing Secrets</a>.</p>
<p><img border="0" src="AddingNewSecrets.png" width="398" height="428"></p>
<p>&nbsp;</p>
<!--This adds space before first level 1 heading-->
<div class="margintop3"></div>
<span class="head3">Refreshing Credentials Stores</span>
<p class="margintop2">Refresh Stores in CASA Manager is used to reload all Secrets from the configured stores.
You can refresh the view of supported stores by pressing F5, or by choosing File->Refresh Stores from the menu.
You can refresh the view of supported stores by pressing F5, or by choosing File > Refresh Stores from the menu.
The miCASA store is supported on Windows* and Linux*. KDE Wallet and GNOME*
Keyring are additional stores supported in Linux*.</p>
<p class="margintop2">
<img border="0" src="RefreshCredentialStores.png" width="303" height="159"></p>
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
<p class="margintop2">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
see <a
href="legal_notices_en.html">Legal Notices</a>.
<p class="marginleft1">
<!--End Content -->
<p></p>
<div class="ruleabove"></div></div>
</body>

30
CASA/gui/help/en/CASAMasterPasswordAuthentication.htm
View File

@ -7,7 +7,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -18,11 +18,13 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Setting Master Password</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">When you start CASA Manager the first time, you are prompted to
<p class="margintop2">When you start CASA Manager for the first time, you are prompted to
create or enter a master password. You are prompted for your master password when
displaying the values of secrets. The master password must be at least eight characters
long.</p>
@ -41,21 +43,21 @@
your new master password, then click OK.</li>
</ol>
<p><img border="0" src="SettingMasterPassword.png" width="369" height="269"></p>
<p><b>Important:</b> To prevent unauthorized access to your credential stores,
always create confidential passwords that are not easily discovered.</p>
<p class="margintop2">See also <a href="ResetMastPW.html" target="_blank">Resetting the CASA Master Password</a>.</p>
<p class="margintop2">
<!--This adds space before first level 1 heading-->
</p>
<div class="margintop3"></div>
<!--End Content -->
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
<p class="margintop2">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
see <a href="legal_notices_en.html">Legal Notices</a>. </p>
<p class="marginleft1">
<!--End Content -->
<div class="ruleabove"><br>
</div>
</div>
</body>
</html>

27
CASA/gui/help/en/Contents.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,17 +16,15 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Contents</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">Common Authentication Services Adapter (CASA) is the
common cross-platform foundation for authentication and single sign-on
services for Novell® Linux* Desktop and Microsoft* Windows* operating systems.
Applications that integrate CASA can securely authenticate and cache
credentials for single sign-on purposes. CASA Manager is the graphical user
interface that enables you to access and manage the authentication credentials
(secrets) of the programs and services installed on any of these platforms. It
provides you a single place to manage credentials for KDE* Wallet, GNOME* Keyring and Firefox* Password Manager stores.</p>
<p class="margintop2">Common Authentication Service Adapter (CASA) is the common
cross-platform foundation for authentication and single sign-on services for
Novell&reg; Linux* Desktop, Microsoft* Windows*, and Macintosh* OS 10 operating
systems. CASA Manageris the graphical user interface that enables you to access
and manage the authentication credentials (secrets) of the programs and services
installed on any of these platforms.</p>
<p class="margintop2">This Help file contains the following topics:</p>
@ -42,7 +40,7 @@
<li><a href="ImportingSecrets.htm" target="_blank">Importing User Secrets</a></li>
<li><a href="LinkingSecrets.htm" target="_blank">Linking Secrets</a></li>
<li><a href="UnlockSecrets.htm" target="_blank">Locking and Unlocking Secrets</a></li>
<li><a href="Persistent_Storage.htm" target="_blank">Persistent Storage</a></li>
<li><a href="PersistentStorage.htm" target="_blank">Persistent Storage</a></li>
<li><a href="ResetMastPW.html" target="_blank">Resetting the CASA Master Password</a></li>
<li><a href="Preferences.htm" target="_blank">Setting CASA Preferences</a></li>
<li><a href="CASAMasterPasswordAuthentication.htm" target="_blank">Setting
@ -59,11 +57,10 @@
create confidential passwords that are not easily broken in order to prevent
unauthorized access.</p>
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
<div class="smalltext">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
see <a
href="legal_notices_en.html">Legal Notices</a>.</div>
<p></p>
<div class="ruleabove"></div>
</div>

2
CASA/gui/help/en/CopyingSecrets.htm
View File

@ -16,8 +16,6 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent" style="left: 8px; top: 37px">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Copying Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->

23
CASA/gui/help/en/DestroyingSecrets.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,25 +16,18 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Destroying Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">Use the following procedure to clear your cache and destroy
all credentials that are stored in the miCASA store:
all credentials that are stored in the miCASA store:</p>
<ul>
<li>Click File &gt; Destroy Secrets, then click OK.</li>
</ul>
Your secrets are restored manually by creating new
secrets or by using applications that are integrated with CASA.<p>
<img border="0" src="DestroyingSecrets.png" width="331" height="145"></p>
</p>
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
</div>
<p class="margintop2">Your secrets are restored manually by creating new
secrets or by using applications that are integrated with CASA</p>
</div>
</body>
</html>

15
CASA/gui/help/en/EditingSecrets.html
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,9 +16,11 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Editing Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">You edit a secret by adding new Key-Value pairs or changing
existing Key-Value pairs:<br>
@ -38,15 +40,8 @@
in the miCASA credential store.<br>
After they are created, Secret ID names cannot be edited.</li>
</ol>
<p><img border="0" src="EditingSecrets.png" width="398" height="414"></p>
<!--End Content -->
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
</div>
<div class="ruleabove"></div></div>
</body>
</html>

2
CASA/gui/help/en/ExportingSecrets.htm
View File

@ -16,8 +16,6 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Exporting User Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->

1
CASA/gui/help/en/FindReplace.htm
View File

@ -16,7 +16,6 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent" style="left: 8px; top: 37px">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Finding and Replacing Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->

1
CASA/gui/help/en/ImportingSecrets.htm
View File

@ -15,7 +15,6 @@
<body bgcolor="white" marginwidth="0" marginheight="0" leftmargin="0" topmargin="0">
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<div id="helpcontent">
<!--Begin Content -->
<div class="head3b">Importing User Secrets</div>

14
CASA/gui/help/en/LinkingSecrets.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,8 +16,9 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Linking Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">You can link two or more secrets so that their respective
@ -49,15 +50,8 @@
in the Existing Linked Keys window, then click the &#151; button. The selected
secret is deleted from the Existing Linked Keys window.</li>
</ol>
<p><img border="0" src="LinkingSecrets.png" width="467" height="590"></p>
<!--End Content -->
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
</div>
<div class="ruleabove"></div></div>
</body>
</html>

28
CASA/gui/help/en/Preferences.htm
View File

@ -7,7 +7,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -18,29 +18,29 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Preferences</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">This option is active only when CASA is installed in a
Linux* environment. Linux provides support for miCASA, KDE* Wallet, GNOME*
Keyring, and Firefox* Password Manager, or all four credential stores. </p>
Linux* environment. Linux provides support for miCASA, KDE Wallet, GNOME*
Keyring, or all three credential stores. </p>
<p class="margintop2">Use the following procedure to specify which credential
stores you want to use:</p>
<ol>
<li>From the CASA Manager page, Click Options &gt; Preferences</li>
<li>Select which credential stores you wish to use (KDE Wallet, GNOME
Keyring, Firefox Password Manager).</li>
<li>Select which credential stores you wish to use (miCASA, KDE Wallet, GNOME
Keyring).</li>
</ol>
<p>In Windows*, miCASA is the only credential store available, so references
to KDE Wallet, GNOME Keyring and Firefox Password Manager are inactive.
<p><img border="0" src="Preferences.png" width="295" height="180"><p>&nbsp;<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
to KDE Wallet and GNOME Keyring are inactive.
<p>A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk
(*) denotes a third-party trademark. For information on trademarks, see <a
href="legal_notices_en.html">Legal Notices</a>.
<!--This adds space before first level 1 heading-->
<p></p>
<div class="ruleabove"></div>
</div>
<div class="ruleabove"></div></div>
</body>
</html>

1
CASA/gui/help/en/ResetMastPW.html
View File

@ -16,7 +16,6 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->

1
CASA/gui/help/en/SingSignOnPref.htm
View File

@ -16,7 +16,6 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent" style="left: 8px; top: 37px">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Assigning Single Sign-on Preferences</div>
<!--Remove this section if you do not need introductory text for this topic -->

13
CASA/gui/help/en/UnlockSecrets.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,8 +16,9 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Locking and Unlocking Secrets</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">To prevent individuals and other applications from viewing
@ -31,13 +32,7 @@
<li>Enter your master password.</li>
</ol>
<!--End Content -->
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A"><u>Legal Notices</u></font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
</div>
<div class="ruleabove"></div></div>
</body>
</html>

15
CASA/gui/help/en/ViewSecrets.htm
View File

@ -5,7 +5,7 @@
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
@ -16,9 +16,11 @@
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent">
<div class="head1">CASA - Common Authentication Services Adapter</div><br>
<!--Begin Content -->
<div class="head3b">Viewing Secret Values</div>
<!--Remove this section if you do not need introductory text for this topic -->
<p class="margintop2">You can view the Key-Value pairs of all secrets cached
in the miCASA credential store.</p>
@ -29,15 +31,8 @@
show the value in clear text, click Show Values in Clear Text, then enter
your master password.</li>
</ol>
<p><img border="0" src="ViewingSecrets.png" width="398" height="414"></p>
<!--End Content -->
<div class="smalltext" style="width: 757; height: 24">
<p align="center"><font color="#4A4A4A">A trademark symbol (®, TM, etc.) denotes a Novell trademark.
An asterisk (*) denotes a third-party trademark. For information on trademarks,
see </font> <a
href="legal_notices_en.html"><font color="#4A4A4A">Legal Notices</font></a><font color="#4A4A4A">.</font></div>
<p></p>
<div class="ruleabove"></div>
</div>
<div class="ruleabove"></div></div>
</body>
</html>

71
CASA/gui/help/en/legal_notices_en.html
View File

@ -2,40 +2,61 @@
<head>
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<title>Novell&reg; CASA Manager</title>
<link href="hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url('help_zcc_bg.gif') repeat-x; }
<title>Novell ZENworks Control Center</title>
<link href="../hf_style.css" rel="styleSheet" type="text/css">
<style type="text/css" media="screen">
<!--
body { font-family: "Trebuchet MS", Arial, Helvetica, Geneva; background: white url(help_zcc_bg.gif) repeat-x 0% 0% }
#headgraphic { position: absolute; z-index: 0; top: 0px; left: 0px; width: 380px; visibility: visible }
#helpcontent { position: absolute; top: 37px; left: 10px; width: 93%; visibility: visible }
-->
</style>
</style>
</head>
<body bgcolor="white" marginwidth="0" marginheight="0" leftmargin="0" topmargin="0">
<div id="headgraphic">
<img src="h1_help_zcc.gif" width="221" height="26" border="0"></div>
<div id="helpcontent" style="left: 10px; width: 68%; top: 37px">
<div class="head1"><b>CASA - Common Authentication Services Adapter</b></div><br>
<div id="helpcontent">
<div class="head3b"><b>Legal Notices</b></div>
Copyright (C) 2005-2006 Novell, Inc. All Rights Reserved.<br/>
This library is free software; you can redistribute it and/or<br/>
modify it under the terms of the GNU Lesser General Public<br/>
License as published by the Free Software Foundation; version 2.1<br/>
of the License.<br/>
<br/>
This library is distributed in the hope that it will be useful,<br/>
but WITHOUT ANY WARRANTY; without even the implied warranty of<br/>
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU<br/>
Library Lesser General Public License for more details.<br/>
<div class="head3b">Legal Notices</div>
You should have received a copy of the GNU Lesser General Public<br/>
License along with this library; if not, Novell, Inc.<br/>
<br/>
To contact Novell about this file by physical or electronic mail,<br/>
you may find current contact information at <a href="http://www.novell.com">www.novell.com</a>.
<div class="ruleabove"></div>
<p><b>Disclaimer</b> <br>
Novell, Inc. makes no representations or warranties with respect to the contents or use of
this documentation and specifically disclaims any express or implied warranties of
merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content, at any time, without
obligation to notify any person or entity of such revisions or changes.</p>
<p>Further, Novell, Inc. makes no representations or warranties with respect to any Novell
software, and specifically disclaims any express or implied warranties of merchantability
or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.</p>
<p><b>Export Notice</b> <br>
You may not use, export, or re-export this product in violation of any applicable
laws or regulations including, without limitation, U.S. export regulations
or the laws of the country in which you reside.
<p><b>Copyright</b> <br>
Copyright &copy; 2005-2007 Novell, Inc. All rights reserved. No part of this publication
may be reproduced, photocopied, stored on a retrieval system, or transmitted
without the express written consent of the publisher.</p>
<p><b>Patents</b> <br>
Novell, Inc. has intellectual property rights relating to technology embodied
in the product that is described in this document. In particular, and without
limitation, these intellectual property rights may include one or more of
the U.S. patents listed at <a href="http://www.novell.com/company/legal/patents/">http://www.novell.com/company/legal/patents/</a>
and one or more additional patents or pending patent applications in the U.S.
and in other countries.</p>
<p><b>Novell Trademarks</b> <br>
Novell, NetWare, and ZENworks are registered trademarks of Novell, Inc. in the United States and
other countries.
<p>eDirectory and Red Carpet are trademarks of Novell, Inc.</p>
<p><b>Third-Party Trademarks</b> <br>
All third-party trademarks are the property of their respective owners.</p>
</div>
</body>
</html>