Versions Compared

Old Version 4

changes.mady.by.user Patrick Ahmed

Saved on

compared with

New Version Current

changes.mady.by.user Kim Rasmussen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Introduction

Ceptor PortalProtect is an entire security solution that protects portals and application servers, regardless of the communication type used, be it JSP, Servlets, EJB or other type of communication. PortalProtect Ceptor can provide Authentication and Authorization checking on all resources, as well as provide secure communication clients and servers.
Any number of web servers, application servers or other types of servers can be integrated, and used to create personalized content and session sharing between all applications, so users experience single signon with access (depending on authorization of course) to all applications available in your portal.
This document describes how to integrate PortalProtect Ceptor with the Tomcat Application Server.

Installation

In the PortalProtect Ceptor distribution, you can find the required .jar files in samples/integration/tomcat. To install the Tomcat Realm, you will need to copy PortalProtectTomcatCeptorTomcat_6.jar or PortalProtectTomcatCeptorTomcat_7.jar depending on your tomcat version to your tomcat lib directory, along with PortalProtectAgentCeptorAgent.jar and slf4j-api-.jar and an implementation of slf4j, e.g. logback-core-.jar and logback-classic-*.jar which are all required by the PortalProtect Ceptor Agent.
You will also need a configuration for the logging framework, e.g. logback.xml – see the PortalProtect Ceptor Distribution for examples which you can copy from.
Then you need to change conf/server.xml and add the following:

...


This will tell tomcat to load the appropriate PortalProtect Ceptor security realm, and the SessionIDValve ensures that the realm has access to the session ID from the cookie in the request.
To configure PortalProtect Ceptor Agent, you will also need to either set the system properties portalprotect.server.name/server.name to the name of the server, and portalprotect.config.servers/config.servers to the list of configuration servers, or you need to provide ptservers.properties in the classpath with these properties.
See more in PortalProtect Users Guide.

Example:
set CATALINA_OPTS=-Dportalprotect.server.name=webserver1 –Dportalprotect.config.servers=localhost:21233

...