Getting Started with WebSphere Application Server

More documents

Recommendations

Info

148 Getting Started with WebSphere Application Server Community Edition In Listing 8.1, you define the user’s id and password pairs. In Listing 8.2 you define the group and user pairs. If there are many users that belong to one group, separate each user id with a comma. Secondly, copy the above files into the /var/security folder. Then input the file names including the relative path as shown in Figure 8.3 Figure 8.3 – Provide the property files for users and groups The Digest Algorithm field indicates the type of encryption that will be used to create the binary representation of the password, such as MD5 or SHA. The Digest Encoding field indicates the text format that will be used to store the binary representation. The two supported formats are HEX and BASE64. Leave both of them empty for this book. 4. Then you can choose Skip Test and Deploy. The new security realm is now visible in the Security Realms portlet in the Community Edition console as illustrated in Figure 8.4. Figure 8.4 – New security realm: helloRealm
Chapter 8 – Security 149 8.3 Implementing security in a Java EE application In general, access to a secured Java EE resource requires the validation of credentials (user ID/password) against the user registry. The user registry by itself does not enforce any security policies or constraints (authorization); it simply validates the supplied user, group, and password information by the Java EE authentication mechanisms. Role-based security allows a developer to secure access to Java EE resources based on roles. Often a developer has no knowledge of the users and groups that will exist at runtime; by using roles, he can grant or revoke access to a specific artifact. Later, an administrator can map these roles to actual users and groups. Java EE has two forms of role-based security: • Declarative security, where the security rules are defined in the deployment descriptors and the Java EE runtime manages access to the Java EE artifact. A user will see all or none of a resource. • Programmatic security, where the program determines the role of a user and grants access to different resources depending on this role. The user may only see a subset of a resource depending on his role. 8.3.1 Defining role mapping The mapping of specific users and groups to roles is defined in the Community Edition deployment plan, which can either be Web, EJB, or EAR. For example, the code snippet shown in Listing 8.3 defines that user bill will take the role as a super user, and the group employee will take the role of general users. Listing 8.3 - Role mappings 8.3.2 Implementing EJB Security This section describes how to implement declarative and programmatic EJB security. 8.3.2.1 Declarative security
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
5 Chapter 5 - Enterprise Java Beans
Page 91 and 92:
1. Define local and remote interfac
Page 93 and 94:
Chapter 5 - Enterprise Java Beans 9
Page 95 and 96:
Chapter 5 - Enterprise Java Beans 9
Page 97 and 98: Note: Chapter 5 - Enterprise Java B
Page 99 and 100: Chapter 5 - Enterprise Java Beans 9
Page 109 and 110: 6 Chapter 6 - Messaging Messaging i
Page 111 and 112: Chapter 6 - Messaging 111 3. Messag
Page 113 and 114: Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116: Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118: Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120: Chapter 6 - Messaging 119 For examp
Page 121 and 122: textMessage.getText()); } catch (JM
Page 123 and 124: Chapter 6 - Messaging 123 3. Copy t
Page 125: Chapter 6 - Messaging 125 D. Messag
Page 128 and 129: 128 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182: 10 Chapter 10 - Tuning a Community
Page 183 and 184: Chapter 10 - Tuning a Community Edi
Page 191 and 192: 10.4.2 Operating system tuning Chap
Page 193: Chapter 10 - Tuning a Community Edi
Page 198 and 199:
198 Getting Started with WebSphere
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 211 and 212:
A Appendix A - Solutions to review
Page 213 and 214:
Appendix A - Solutions to review qu
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
B Appendix B - Up and running with
Page 221 and 222:
Appendix B - Up and running with DB
Page 223 and 224:
4. The following is performed by de
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235:
C Appendix C - Using the sample cod
Page 238 and 239:
Page 240:
show all

Getting Started with WebSphere Application Server

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?