This section discusses some of the methods by which you can protect data and restrict access to resources.
Protecting ports and listeners You can provide various levels of security to EAServer listeners by assigning security profiles to HTTPS and IIOPS listeners. See Chapter 13, “Security Configuration Tasks” for more information.
Protecting application server resources and securing clients EAServer provides several methods to protect server resources and secure client/server connections:
Set authentication and authorization levels using EAServer Manager. See Chapter 3, “Using Web Application Security.”
Create custom authentication and authorization components. See Chapter 10, “Creating and Using Custom Security Components.”
Use the Java authentication and authorization service (JAAS). See Chapter 11, “Using the JAAS API.”
Use SSL to protect your Java, C++, and ActiveX clients. See Chapter 5, “Using SSL in Java Clients,” Chapter 6, “Using SSL in C++ Clients,” and Chapter 8, “Using SSL in ActiveX Clients”.
Establish minimum levels of protection for components, packages, and methods using quality of protection (QOP). See Chapter 2, “Securing Component Access.”
Propagate client principal information from one server to another and use run-as support so an EJB can perform method invocations on other EJBs using a different identity. See Chapter 2, “Securing Component Access.”
Protecting data Use public-key certificates when exchanging sensitive data over a network to protect it from being viewed by intruders. See Chapter 14, “Managing Keys and Certificates” for more information.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
