JBoss Enterprise Application Platform Common Criteria Certification ...

More documents

Recommendations

Info

32 Chapter 6. The JNDI Naming Service example shows the section of the http-invoker.sarjboss-service.xml descriptor that the example installs to provide this configuration. All that has changed relative to the standard HTTP configuration are the InvokerURLPrefix and InvokerURLSuffix attributes, which setup an HTTPS URL using the 8443 port. jboss:service=Naming https:// :8443/invoker/JMXInvokerServlet true org.jnp.interfaces.Naming org.jboss.proxy.ClientMethodInterceptor org.jboss.proxy.SecurityInterceptor org.jboss.naming.interceptors.ExceptionInterceptor org.jboss.invocation.InvokerInterceptor At a minimum, a JNDI client using HTTPS requires setting up a HTTPS URL protocol handler. We will be using the Java Secure Socket Extension (JSSE) for HTTPS. The JSSE documentation does a good job of describing what is necessary to use HTTPS, and the following steps were needed to configure the example client shown in Example 6.2, “A JNDI client that uses HTTPS as the transport”: A protocol handler for HTTPS URLs must be made available to Java. The JSSE release includes an HTTPS handler in the com.sun.net.ssl.internal.www.protocol package. To enable the use of HTTPS URLs you include this package in the standard URL protocol handler search property, java.protocol.handler.pkgs. We set the java.protocol.handler.pkgs property in the Ant script. The JSSE security provider must be installed in order for SSL to work. This can be done either by installing the JSSE jars as an extension package, or programatically. We use the programatic approach in the example since this is less intrusive. Line 18 of the ExClient code demonstrates how this is done. The JNDI provider URL must use HTTPS as the protocol. Lines 24-25 of the ExClient code specify an HTTP/SSL connection to the localhost on port 8443. The hostname and port are defined by the web container SSL connector. The validation of the HTTPS URL hostname against the server certificate must be disabled. By default, the JSSE HTTPS protocol handler employs a strict validation of the hostname portion of the HTTPS URL against the common name of the server certificate. This is the same check done by web browsers when you connect to secured web site. We are using a self-signed server certificate that uses a common name of "Chapter 8 SSL Example" rather than a particular hostname, and this is likely to be common in development environments or intranets. The JBoss HttpInvokerProxy will override the default hostname checking if a org.jboss.security.ignoreHttpsHost system property exists and has a value of true. We set the org.jboss.security.ignoreHttpsHost property to true in the Ant script.
Example 6.2. A JNDI client that uses HTTPS as the transport package org.jboss.chap3.ex1; import java.security.Security; import java.util.Properties; import javax.naming.Context; import javax.naming.InitialContext; public class ExClient { public static void main(String args[]) throws Exception { Properties env = new Properties(); env.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.HttpNamingContextFactory"); env.setProperty(Context.PROVIDER_URL, "https://localhost:8443/invoker/JNDIFactorySSL"); } JBoss Enterprise Application Platform Common Criteria Certification 5 Administration And Configuration Guide 33 } Context ctx = new InitialContext(env); System.out.println("Created InitialContext, env=" + env); Object data = ctx.lookup("jmx/invoker/RMIAdaptor"); System.out.println("lookup(jmx/invoker/RMIAdaptor): " + data); To test the client, first build the chapter 3 example to create the chap3 configuration fileset. [examples]$ ant -Dchap=naming config Next, start the JBoss server using the naming configuration fileset: [bin]$ sh run.sh -c naming And finally, run the ExClient using: [examples]$ ant -Dchap=naming -Dex=1 run-example ... run-example1: [java] Created InitialContext, env={java.naming. \ provider.url=https://localhost:8443/invoker/JNDIFactorySSL, java.naming. \ factory.initial=org.jboss.naming.HttpNamingContextFactory} [java] lookup(jmx/invoker/RMIAdaptor): org.jboss.invocation.jrmp. \ interfaces.JRMPInvokerP roxy@cac3fa 6.4 .3. Securing Access to JNDI over HTTP One benefit to accessing JNDI over HTTP is that it is easy to secure access to the JNDI InitialContext factory as well as the naming operations using standard web declarative security. This is possible because the server side handling of the JNDI/HTTP transport is implemented with two servlets. These servlets are included in the http-invoker.sar/invoker.war directory found in the default and all configuration deploy directories as shown previously. To enable secured access to JNDI you need to edit the invoker.war/WEB-INF/web.xml descriptor and remove all unsecured servlet mappings. For example, the web.xml descriptor shown in Example 6.3, “An example web.xml descriptor for secured access to the JNDI servlets” only allows access to the invoker.war servlets if the user has been authenticated and has a role of HttpInvoker.
Page 1 and 2: JBoss Enterprise Application Platfo
Page 3 and 4: Abstract JBoss Enterprise Applicati
Page 11 and 12: Chapter 1. Introduction JBoss Enter
Page 19 and 20: Chapter 4. Deployment Deploying app
Page 21 and 22: web JBoss Enterprise Application Pl
Page 23 and 24: Chapter 6. The JNDI Naming Service
Page 31: JBoss Enterprise Application Platfo
Page 53 and 54: @XmlAccessorType(XmlAccessType.FIEL
Page 57 and 58: 7.15. WebServiceContext The WebServ
Page 59 and 60: ** * The getPort method returns a p
Page 61 and 62: Message Payload In this mode, clien
Page 71 and 72: @WebServiceClient(name = "EchoServi
Page 73 and 74: @WebService(name = "StatefulEndpoin
Page 83 and 84:
JBoss Enterprise Application Platfo
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
** * Creates a Jaxr Organization wi
Page 91 and 92:
Page 93 and 94:
** * Annotation for specifying the
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
that have not completed after a spe
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Oracle 10g: org.hibernate.dialect.O
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
That's it; that's all it takes to g
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Application Platform ships with a d
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
ean. By default true, since replica
Page 165 and 166:
a different physical host. If not a
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
deployment (war, ear, jar, whatever
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
The available attributes in the FD
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
import org.jboss.ha.cachemanager.Ca
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Example A.10. Sybase Datasource [ 1
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Example A.25. PostgreSQL XA Datasou
Page 255 and 256:
Example B.2. Filtering App1 Log Out
show all

JBoss Enterprise Application Platform Common Criteria Certification ...

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

Delete template?

Save as template?