Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The general approach is:</p> <p>1) Subclass AbstractAuthenticationToken for your XML logins, let's call it XMLAuthenticationToken.</p> <p>2) Subclass AbstractAuthenticationProcessingFilter and add it to the filter chain after UsernamePasswordAuthenticationFilter. It should create a XMLAuthenticationToken based on the data in the XML. You can use UsernamePasswordAuthenticationFilter as an example for the general structure of the filter (that's most likely the filter that you are currently using for your regular Spring Security logins).</p> <pre><code>&lt;http&gt; &lt;custom-filter after="FORM_LOGIN_FILTER" ref="xmlAuthenticationFilter"/&gt; &lt;/http&gt; </code></pre> <p>The filter should set a filterProcessesUrl that is different from the UsernamePasswordFilter. This is the URL the external system will post the XML to. For example:</p> <pre><code>public XmlAuthenticationFilter() { super("/xml_security_check"); } </code></pre> <p>3) Subclass AbstractUserDetailsAuthenticationProvider. Have it look up the user from the UserDetailsService based on the info in the token, and then authenticate it. Use DaoAuthenticationProvider as an example. You will need to register the new provider with the AuthenticationManager.</p> <pre><code>&lt;authentication-manager&gt; &lt;authentication-provider user-service-ref='myUserDetailsService'/&gt; &lt;authentication-provider ref="xmlAuthenticationProvider" /&gt; &lt;/authentication-manager&gt; </code></pre> <p>You might be able to get away with reusing UsernamePasswordAuthenticationToken (for #1, it has a nice "details" extension mechanism) and DaoAuthenticationProvider (or subclassing it) for #3.</p>
    singulars
    1. This table or related slice is empty.
    1. POIntegrate Single Sign On using Spring Security
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsourcedelica
    1. USsourcedelica
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIntegrate Single Sign On using Spring Security
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTModeratorReview
    1. COthanks, I'll give it a shot tonight. appreciate the assistance.
      singulars
      1. PO
      1. USc12
    2. COericacm how do I configure my application to use this form of authentication vs the form based method. I have a link for both inside the app but how does Spring do the mapping?
      singulars
      1. PO
      1. USc12
    3. COBy adding the new filter to the chain and adding the new provider to the AuthenticationManager. I added examples of how to do this to #2 and #3.
      singulars
      1. PO
      1. USsourcedelica
 

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