Resolved inconsistencies between the spec files and the SuSE PDB entries

for package summaries and descriptions.
This commit is contained in:
Juan Carlos Luciani
2007-02-20 16:20:05 +00:00
parent 493ce1a9fe
commit 37c2d94ec9
3 changed files with 80 additions and 82 deletions

View File

@@ -26,7 +26,7 @@ Autoreqprov: on
%define bldno @VERSION@
Version: @VERSION@
Release: 0
Summary: Novell Common Authentication Services Adapter Authentication Token Infrastructure "Java" (CASA_auth_token)
Summary: Novell CASA Authentication Token Service
Source: %{name}-%{version}.tar.bz2
BuildRoot: %{_tmppath}/%{name}-%{version}-build
Requires: jre >= 1.5.0
@@ -37,40 +37,40 @@ PreReq: /usr/sbin/groupadd, /usr/sbin/useradd, /usr/sbin/userdel, /usr/bi
BuildArchitectures: noarch
%description
CASA_auth_token is an authentication token infrastructure with support for multiple
authentication mechanisms with an emphasis on providing a scalable single
sign-on solution.
CASA_auth_token is an authentication token infrastructure with support for
multiple authentication mechanisms with an emphasis on providing a scalable
single sign-on solution.
A key feature of CASA_auth_token is that its authentication tokens contain identity
information about the entity being authenticated. This information is made available
to the consuming services. The amount of information contained in the tokens is
configured on a per-service basis. Because of this feature, we say that CASA_auth_token
projects an "Authenticated Identity".
A key feature of CASA_auth_token is that its authentication tokens contain
identity information about the entity being authenticated. This information is
made available to the consuming services. The amount of information contained in
the tokens is configured on a per-service basis. Because of this feature, we say
that CASA_auth_token projects an "Authenticated Identity".
The CASA_auth_token_svc is the infrastructure component responsible for authenticating
entities using the native authentication mechanism and for issuing tokens that can later
be used by applications to authenticate the entity o services that are CASA authentication
enabled.
The CASA_auth_token_svc is the infrastructure component responsible for
authenticating entities using the native authentication mechanism and for issuing
tokens that can later be used by applications to authenticate the entity or
services that are CASA authentication enabled.
%package -n CASA_auth_token_jaas_support
Summary: Libraries needed for JAAS applications development.
Summary: Novell CASA Authentication Token JAAS Support Components
Group: Applications/System
Requires: jre >= 1.5.0
%description -n CASA_auth_token_jaas_support
CASA_auth_token is an authentication token infrastructure with support for multiple
authentication mechanisms with an emphasis on providing a scalable single
sign-on solution.
CASA_auth_token is an authentication token infrastructure with support for
multiple authentication mechanisms with an emphasis on providing a scalable
single sign-on solution.
A key feature of CASA_auth_token is that its authentication tokens contain identity
information about the entity being authenticated. This information is made available
to the consuming services. The amount of information contained in the tokens is
configured on a per-service basis. Because of this feature, we say that CASA_auth_token
projects an "Authenticated Identity".
A key feature of CASA_auth_token is that its authentication tokens contain
identity information about the entity being authenticated. This information is
made available to the consuming services. The amount of information contained in
the tokens is configured on a per-service basis. Because of this feature, we say
that CASA_auth_token projects an "Authenticated Identity".
The CASA_auth_token_jaas_support package contains the CASA (Common Authentication
Services Adapter) authentication token infrastructure JAAS module and supporting libraries
for token verification.
Services Adapter) authentication token infrastructure JAAS module and supporting
libraries for token verification.
%prep
%setup -q