JBoss Enterprise Application Platform Common Criteria Certification ...

More documents

Recommendations

Info

34 Chapter 6. The JNDI Naming Service Example 6.3. An example web.xml descriptor for secured access to the JNDI servlets JMXInvokerServlet org.jboss.invocation.http.servlet.InvokerServlet 1 JNDIFactory org.jboss.invocation.http.servlet.NamingFactoryServlet namingProxyMBean jboss:service=invoker,type=http,target=Naming proxyAttribute Proxy 2 JNDIFactory /restricted/JNDIFactory/* JMXInvokerServlet /restricted/JMXInvokerServlet/* HttpInvokers An example security config that only allows users with the role HttpInvoker to access the HTTP invoker servlets /restricted/* GET POST HttpInvoker BASIC JBoss HTTP Invoker HttpInvoker The web.xml descriptor only defines which sevlets are secured, and which roles are allowed to access the secured servlets. You must additionally define the security domain that will handle the authentication and authorization for the war. This is done through the jboss-web.xml descriptor, and an example that uses the http-invoker security domain is given below. java:/jaas/http-invoker
JBoss Enterprise Application Platform Common Criteria Certification 5 Administration And Configuration Guide 35 The security-domain element defines the name of the security domain that will be used for the JAAS login module configuration used for authentication and authorization. 6.4 .4 . Securing Access to JNDI with a Read-Only Unsecured Context Another feature available for the JNDI/HTTP naming service is the ability to define a context that can be accessed by unauthenticated users in read-only mode. This can be important for services used by the authentication layer. For example, the SRPLoginModule needs to lookup the SRP server interface used to perform authentication. The rest of this section explains how read-only works in JBoss Enterprise Application Platform. First, the ReadOnlyJNDIFactory is declared in invoker.sar/WEB-INF/web.xml. It will be mapped to /invoker/ReadOnlyJNDIFactory. ReadOnlyJNDIFactory A servlet that exposes the JBoss JNDI Naming service stub through http, but only for a single read-only context. The return content is serialized MarshalledValue containing the org.jnp.interfaces.Naming stub. org.jboss.invocation.http.servlet.NamingFactoryServlet namingProxyMBean jboss:service=invoker,type=http,target=Naming,readonly=true proxyAttribute Proxy 2 ReadOnlyJNDIFactory /ReadOnlyJNDIFactory/* The factory only provides a JNDI stub which needs to be connected to an invoker. Here the invoker is jboss:service=invoker,type=http,target=Naming,readonly=true. This invoker is declared in the http-invoker.sar/META-INF/jboss-service.xml file. jboss:service=Naming http:// :8080/invoker/readonly/JMXInvokerServlet true org.jnp.interfaces.Naming org.jboss.proxy.ClientMethodInterceptor org.jboss.proxy.SecurityInterceptor org.jboss.naming.interceptors.ExceptionInterceptor org.jboss.invocation.InvokerInterceptor The proxy on the client side needs to talk back to a specific invoker servlet on the server side. The configuration here has the actual invocations going to /invoker/readonly/JMXInvokerServlet. This is actually the standard JMXInvokerServlet with a read-only filter attached.
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 33: Example 6.2. A JNDI client that use
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 85 and 86:
JBoss Enterprise Application Platfo
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 ...

Create successful ePaper yourself

Delete template?

Save as template?