Download PDF - IBM Redbooks

J2EE
Client
0
Web
Client
0
In Figure 1-4, we show numbers for each stop the Web client and the J2EE client
make as they go through the connection path to reach CICS.
Web
Server
1
Figure 1-4 Security checkpoint internal flow
Web
Container
In each case the number zero (0) represents the initial point before doing
anything, and WAS and CICS are local to each other, meaning that they are on
the same LPAR on z/OS.
For the Web client, authentication would be attempted at 1, 2, 4, and 5.
Authorization would be attempted at 2, 3, 4, and 5.
For the J2EE client, authentication would be attempted at 1, 2, 3, and similarly
authorization would be attempted at 1, 2, and 3.
To fully understand the security flow on the HTTP(s) and IIOP layers, it requires
deep understanding of the specification and architecture of these protocols.
Once TCP/IP delivers the data, the HTTP(s) and the IIOP code must parse and
interpret the HTTP and GIOP (IIOP) headers in order to take an appropriate
security action.
We do not discuss the HTTP(s) and IIOP internal flow here in this book, but the
security mechanisms implemented to secure HTTP and IIOP protocols are
discussed later on.
1.3.2 Web client authentication overview
2
EJB
Container
Authentication is performed using user information stored in a user account
repository and based on the protocol the user uses to access WAS.
3
1
4
2
J2C
CICS
Chapter 1. Introduction 15
3
5