Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 589171 Details for
Bug 828305
Jboss ESB expose as web service using SOAP over HTTPs
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
server.xml
server.xml (text/xml), 9.12 KB, created by
Ravi
on 2012-06-04 14:26:04 UTC
(
hide
)
Description:
server.xml
Filename:
MIME Type:
Creator:
Ravi
Created:
2012-06-04 14:26:04 UTC
Size:
9.12 KB
patch
obsolete
><Server> > > <!-- Optional listener which ensures correct init and shutdown of APR, > and provides information if it is not installed --> > <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" /> > <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html --> > <Listener className="org.apache.catalina.core.JasperListener" /> > > <Service name="jboss.web"> > > <!-- A HTTP/1.1 Connector on port 8080 --> > <Connector protocol="HTTP/1.1" port="8080" address="${jboss.bind.address}" > connectionTimeout="20000" redirectPort="8443" /> > > <!-- Add this option to the connector to avoid problems with > .NET clients that don't implement HTTP/1.1 correctly > restrictedUserAgents="^.*MS Web Services Client Protocol 1.1.4322.*$" > --> > > <!-- A AJP 1.3 Connector on port 8009 --> > <Connector protocol="AJP/1.3" port="8009" address="${jboss.bind.address}" > redirectPort="8443" /> > > <!-- SSL/TLS Connector configuration using the admin devl guide keystore > <Connector protocol="HTTP/1.1" SSLEnabled="true" > port="8443" address="${jboss.bind.address}" > scheme="https" secure="true" clientAuth="false" > keystoreFile="${jboss.server.home.dir}/conf/chap8.keystore" > keystorePass="rmi+ssl" sslProtocol = "TLS" /> > --> > <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" > maxThreads="150" scheme="https" secure="true" > clientAuth="false" sslProtocol="TLS" > keyAlias="webservice_proxy_security" > keystoreFile="D:/JBossLab/Jboss_SOA_1/jboss-soa-p-5/jboss-as/samples/quickstarts/webservice_proxy_security/build/webservice_proxy_security.keystore" > keystorePass="webservice_proxy_security_pass" > truststoreFile="D:/JBossLab/Jboss_SOA_1/jboss-soa-p-5/jboss-as/samples/quickstarts/webservice_proxy_security/build/webservice_proxy_security.keystore" > truststorePass="webservice_proxy_security_pass" > /> > <Engine name="jboss.web" defaultHost="localhost"> > > <!-- The JAAS based authentication and authorization realm implementation > that is compatible with the jboss 3.2.x realm implementation. > - certificatePrincipal : the class name of the > org.jboss.security.auth.certs.CertificatePrincipal impl > used for mapping X509[] cert chains to a Princpal. > - allRolesMode : how to handle an auth-constraint with a role-name=*, > one of strict, authOnly, strictAuthOnly > + strict = Use the strict servlet spec interpretation which requires > that the user have one of the web-app/security-role/role-name > + authOnly = Allow any authenticated user > + strictAuthOnly = Allow any authenticated user only if there are no > web-app/security-roles > --> > <Realm className="org.jboss.web.tomcat.security.JBossWebRealm" > certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping" > allRolesMode="authOnly" > /> > <!-- A subclass of JBossSecurityMgrRealm that uses the authentication > behavior of JBossSecurityMgrRealm, but overrides the authorization > checks to use JACC permissions with the current java.security.Policy > to determine authorized access. > - allRolesMode : how to handle an auth-constraint with a role-name=*, > one of strict, authOnly, strictAuthOnly > + strict = Use the strict servlet spec interpretation which requires > that the user have one of the web-app/security-role/role-name > + authOnly = Allow any authenticated user > + strictAuthOnly = Allow any authenticated user only if there are no > web-app/security-roles > <Realm className="org.jboss.web.tomcat.security.JaccAuthorizationRealm" > certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping" > allRolesMode="authOnly" > /> > --> > > <Host name="localhost"> > > <!-- Uncomment to enable request dumper. This Valve "logs interesting > contents from the specified Request (before processing) and the > corresponding Response (after processing). It is especially useful > in debugging problems related to headers and cookies." > --> > <!-- > <Valve className="org.apache.catalina.valves.RequestDumperValve" /> > --> > > <!-- Access logger --> > <!-- > <Valve className="org.apache.catalina.valves.AccessLogValve" > prefix="localhost_access_log." suffix=".log" > pattern="common" directory="${jboss.server.log.dir}" > resolveHosts="false" /> > --> > > <!-- Uncomment to enable single sign-on across web apps > deployed to this host. Does not provide SSO across a cluster. > > If this valve is used, do not use the JBoss ClusteredSingleSignOn > valve shown below. > > A new configuration attribute is available beginning with > release 4.0.4: > > cookieDomain configures the domain to which the SSO cookie > will be scoped (i.e. the set of hosts to > which the cookie will be presented). By default > the cookie is scoped to "/", meaning the host > that presented it. Set cookieDomain to a > wider domain (e.g. "xyz.com") to allow an SSO > to span more than one hostname. > --> > <!-- > <Valve className="org.apache.catalina.authenticator.SingleSignOn" /> > --> > > <!-- Uncomment to enable single sign-on across web apps > deployed to this host AND to all other hosts in the cluster. > > If this valve is used, do not use the standard Tomcat SingleSignOn > valve shown above. > > Valve uses a JBossCache instance to support SSO credential > caching and replication across the cluster. The JBossCache > instance must be configured separately. See the > "jboss-web-clusteredsso-beans.xml" file in the > server/all/deploy directory for cache configuration details. > > Besides the attributes supported by the standard Tomcat > SingleSignOn valve (see the Tomcat docs), this version also > supports the following attributes: > > cookieDomain see non-clustered valve above > > cacheConfig Name of the CacheManager service configuration > to use for the clustered SSO cache. See > deploy/cluster/jboss-cache-manager.sar/META-INF/jboss-cache-manager-jboss-beans.xml > Default is "clustered-sso". > > treeCacheName Deprecated. Use "cacheConfig". > JMX ObjectName of the JBoss Cache MBean used to > support credential caching and replication across > the cluster. Only used if no cache can be located > from the CacheManager service using the "cacheConfig" > attribute (or its default value). If not set, the > default is "jboss.cache:service=TomcatClusteringCache" > > maxEmptyLife The maximum number of seconds an SSO with no > active sessions will be usable by a request > > processExpiresInterval The minimum number of seconds between > efforts by the valve to find and invalidate > SSO's that have exceeded their 'maxEmptyLife'. > Does not imply effort will be spent on such > cleanup every 'processExpiresInterval'. > --> > <!-- > <Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" /> > --> > > <!-- Check for unclosed connections and transaction terminated checks > in servlets/jsps. > > Important: The dependency on the CachedConnectionManager > in META-INF/jboss-service.xml must be uncommented, too > --> > > <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve" > cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager" > transactionManagerObjectName="jboss:service=TransactionManager" /> > > </Host> > </Engine> > > </Service> > ></Server>
<b>You cannot view the attachment while viewing its details because your browser does not support IFRAMEs. <a href="attachment.cgi?id=589171">View the attachment on a separate page</a>.</b>
View Attachment As Raw
Actions:
View
Attachments on
bug 828305
:
589169
| 589171