WSSE implementation without SALT not working #8915
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode
8000
characters
I implemented the WSSE token in Symfony 2 using *SHA512* algorithm *WITH* salt. Because bcrypt, without specifying the salt, generates one every time encodes a password, the hash_equals at the end of the AuthenticationProvider won't return TRUE ever. That's because a client encodes the password without a salt, generating a different hash stored in the database. When comparing ONLY these hashes, the password validates. But when concatenating with nonce, created and encode/decoding base64, the hashed won't match: $expected = base64_encode(sha1(base64_decode($nonce).$created.$secret, true)); So the salt it should be mentioned in the article.
Member
|
@sergiu-popa thanks for this ... but this article is too complex and not really necessary most of the times, so we've decided to remove it entirely. See #8943. I'm sorry because this was going to be your first contribution to Symfony Docs ... but I'm sure there will be more opportunities to contribute. Thanks! |
Author
|
@javiereguiluz, is there another article about implementing some type of token authentication for mobile apps? If not, could we leave this online with the details I specified? I know it’s complex, but it’s well-written and explained... and following it I managed to implement it in Symfony 4. I’m using this authentication between a SF4 app and Android/iOS app. Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I implemented the WSSE token in Symfony 2 using SHA512 algorithm WITH salt. Because bcrypt, without specifying the salt, generates one every time encodes a password, the hash_equals at the end of the AuthenticationProvider won't return TRUE ever.
That's because a client encodes the password without a salt, generating a different hash stored in the database. When comparing ONLY these hashes, the password validates. But when concatenating with nonce, created and encode/decoding base64, the hashed won't match:
$expected = base64_encode(sha1(base64_decode($nonce).$created.$secret, true));
So the salt it should be mentioned in the article.