Continuation of changes to switch over to using log4j.
This commit is contained in:
@@ -56,6 +56,7 @@ services that are CASA authentication enabled.
|
||||
Summary: Novell CASA Authentication Token JAAS Support Components
|
||||
Group: Applications/System
|
||||
Requires: jre >= 1.5.0
|
||||
Requires: log4j
|
||||
|
||||
%description -n CASA_auth_token_jaas_support
|
||||
CASA_auth_token is an authentication token infrastructure with support for
|
||||
@@ -241,8 +242,6 @@ fi
|
||||
%stop_on_removal casa_atsd
|
||||
|
||||
%postun
|
||||
%stop_on_update casa_atsd
|
||||
|
||||
# Always undeploy our webapp to force re-deployment on upgrade cases
|
||||
echo "Cleaning up webapp folders"
|
||||
rm -drf /srv/www/casaats/webapps/CasaAuthTokenSvc
|
||||
|
||||
@@ -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 CASA_auth_token_svc jdk novell-zenworks-java-links
|
||||
Requires: jre >= 1.5.0 CASA_auth_token_svc jdk novell-zenworks-java-links log4j
|
||||
|
||||
%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
|
||||
@@ -242,16 +242,14 @@ fi
|
||||
|
||||
%postun
|
||||
# Always undeploy our webapp to force re-deployment on upgrade cases
|
||||
echo "Cleaning up webapp folders"
|
||||
rm -drf /srv/www/casaats/webapps/CasaAuthTokenSvc
|
||||
rm -drf /srv/www/casaats/work/Catalina
|
||||
rm -f /srv/www/casaats/conf/server.xml
|
||||
|
||||
%restart_on_update casa_atsd
|
||||
%insserv_cleanup
|
||||
|
||||
# Do not do anything else if this is an upgrade
|
||||
if test "$1" == 1; then
|
||||
exit 0
|
||||
fi
|
||||
|
||||
|
||||
%files
|
||||
%defattr(-,root,root)
|
||||
|
||||
Reference in New Issue
Block a user