Note that there are some explanatory texts on larger screens.

plurals
  1. POChanges to JBoss web.xml have no effect
    primarykey
    data
    text
    <p>I just added this to my web.xml on my JBOSS server. But it had no effect. I am still allowed to connect to ports that do not use bi-directional certificate exchange. Anyone have an ideas?</p> <pre><code>&lt;!-- Force SSL for entire site as described here: http://wiki.metawerx.net/wiki/ForcingSSLForSectionsOfYourWebsite --&gt; &lt;security-constraint&gt; &lt;!-- defines resources to be protected (in this case everything)--&gt; &lt;web-resource-collection&gt; &lt;!-- name for the resource, can be anything you like --&gt; &lt;!-- Question: is this referenced anywhere else? --&gt; &lt;web-resource-name&gt; Entire Application &lt;/web-resource-name&gt; &lt;!-- protect the entire application --&gt; &lt;url-pattern&gt; /* &lt;/url-pattern&gt; &lt;/web-resource-collection&gt; &lt;!-- defines protection level for protected resource --&gt; &lt;user-data-constraint&gt; &lt;!-- data cannot be observed or changed --&gt; &lt;!-- how it works in tomcat: --&gt; &lt;!-- if (set to integral or confidential &amp;&amp; not using ssl) --&gt; &lt;!-- redirect sent to client, redirecting them to same url --&gt; &lt;!-- but using the port defined in the redirect port --&gt; &lt;!-- attribute in the &lt;Connector&gt; element of server.xml --&gt; &lt;!-- default is 443, so in other words user is redirected --&gt; &lt;!-- to same page using ssl. --&gt; &lt;!-- BUT it is differnt for JBOSS!! See this link: http://wiki.metawerx.net/wiki/ForcingSSLForSectionsOfYourWebsite --&gt; &lt;transport-guarantee&gt; CONFIDENTIAL &lt;/transport-guarantee&gt; &lt;/user-data-constraint&gt; &lt;/security-constraint&gt; &lt;login-config&gt; &lt;!-- Client-side SSL certificate based authentication. The cert is passed to the server to authenticate --&gt; &lt;!-- I am pretty sure that CLIENT-CERT should have a dash NOT an underscore see: http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg139845.html --&gt; &lt;!-- CLIENT-CERT uses a client's AND server's certificates. See: http://monduke.com/2006/01/19/the-mysterious-client-cert/ --&gt; &lt;auth-method&gt; CLIENT-CERT &lt;/auth-method&gt; &lt;/login-config&gt; </code></pre> <hr> <h1>Update</h1> <p>Actually it appears that I have made an error in my original posting. </p> <p>The web.xml does block users from connecting to the webservice using http (port C below). However users are still allowed to connect to ports that do not force users to authenticate themselves (port B). I think that users should be able to connect to port A (it has <code>clientAuth="true"</code>) but I dont think that people should be able to connect to port B (it has <code>clientAuth="false"</code>). </p> <p>Excerpt from server.xml</p> <pre><code> &lt;Connector port="&lt;A&gt;" ... SSLEnabled="true" ... scheme="https" secure="true" clientAuth="true" keystoreFile="... .keystore" keystorePass="pword" truststoreFile="... .keystore" truststorePass="pword" sslProtocol="TLS"/&gt; &lt;Connector port="&lt;B&gt;" ... SSLEnabled="true" ... scheme="https" secure="true" clientAuth="false" keystoreFile="... .keystore" keystorePass="pword" sslProtocol = "TLS" /&gt; &lt;Connector port="&lt;C&gt;" ... /&gt; </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload