Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You haven't actually said what goes wrong, but the authentication code should be exactly the same as for the non-hashed version.</p> <p>If you have a hashed password in the database and the corresponding encoder injected into the authentication provider, the password supplied by the user will be hashed by the encoder before comparing it with the database version.</p> <p>Make sure:</p> <ol> <li>You use the unhashed password value when creating the <code>UsernamePasswordAuthenticationToken</code></li> <li>The value in the database really is the same as the hash produced by the encoder. Load it yourself and check it in a test. The database might be storing it in upper case, for example.</li> </ol> <p>Also, you should probably choose something better than plain MD5. You might want to look at bcrypt, for example, which is supported in Spring Security 3.1 and automatically uses a random salt value. </p> <p><strong>Update</strong></p> <p>Your suggestion of creating a provider which accepts hashed passwords is not a good one. This would allow anyone who steals a password hash to authenticate with it directly (thus defeating the purpose of hashing in the first place).</p> <p>Just validate your email URL links, load the information for that user and create an <code>Authentication</code> object for them:</p> <pre><code>UserDetails user = ... // load user here Authentication a = new UsernamePasswordAuthenticationToken(user, null, user.getAuthorities()); SecurityContextHolder.getContext().setAuthentication(a); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAuthentication in Spring Security whith encoded password
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USShaun the Sheep
    1. USShaun the Sheep
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAuthentication in Spring Security whith encoded password
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe problem is in 1. When creating the UsernamePasswordAuthenticationToken I have only hashed version of password as I load UserDetails object from DB(in my case - by confirmation key)
      singulars
      1. PO
      1. USvacuum
    2. COUsing the stored password won't authenticate the user (which I assume is what you are trying to do). If not, you'll need to clarify what you're trying to achieve. There's not much point in calling the authentication manager with a password which you know is correct in advance.
      singulars
      1. PO
      1. USShaun the Sheep
    3. COI am trying to authenticate user, who clicked on a link from registration email. So UserDetails object came from DB by confirmation key which came from confirm link in email.
      singulars
      1. PO
      1. USvacuum
 

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