Databases
StackOverflow2013
Postsdbo
POSOAP web service and Spring Security
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSOAP web service and Spring Security
    primarykey
    data
    text
    <p>I'm trying to secure a SOAP web service with Spring Security 3.</p> <p>This is my configuration:</p> <pre><code>&lt;jee:jndi-lookup id="dataSource" jndi-name="jdbc/myDB" expected-type="javax.sql.DataSource" /&gt; &lt;http authentication-manager-ref="authenticationManager"&gt; &lt;intercept-url pattern="/**" access="ROLE_USER" requires-channel="https" /&gt; &lt;http-basic /&gt; &lt;logout logout-url="/logout" delete-cookies="JSESSIONID" /&gt; &lt;/http&gt; &lt;authentication-manager id="authenticationManager"&gt; &lt;authentication-provider&gt; &lt;jdbc-user-service data-source-ref="dataSource" /&gt; &lt;/authentication-provider&gt; &lt;/authentication-manager&gt; </code></pre> <p>Tomcat is configured for SSL, a keystore containing the server's private key is used. I'm testing the web service with SOAPUI. I've created a request that perform one of the operation provided by the service. In the Auth section, I've added the username and password of the test user according to the value present in the database. After sending the request, I expect that a session is created and that there is no need to authenticate again. In the HTTP response, the JSESSIONID cookie is present. When a web site is secured by the same mechanism, the user enters its credentials only once until its session is expired when he needs to reauthenticate.</p> <p>What's wrong with my config?</p> <hr> <p>EDIT: I forgot to add that when I resend the same request multiple times, the received JSESSIONID cookie has always a different value. Should I expect it to be the same for a given session?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMickael Marrache
    1. USMickael Marrache
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POSOAP web service and Spring Security
      1. USye9ane
      1. VTFavorite
    1. COIs SoapUI correctly sending back the cookie?
      singulars
      1. POSOAP web service and Spring Security
      1. USartbristol
    2. CO@artbristol It seems that a new JSESSIONID cookie is generated for each message sent by SOAPUI. I don't know why.
      singulars
      1. POSOAP web service and Spring Security
      1. USMickael Marrache
    3. COThat'll be because SoapUI isn't returning the original cookie with each new request.
      singulars
      1. POSOAP web service and Spring Security
      1. USartbristol
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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