-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not really an issue...XSS #107
Comments
Funny. I had it working without Do you mean WSSE auth? There are plenty of authentications at SOAP. Specify the requirements. |
Well as I said, it's not and issue, that how it should work, and It does:) I meant WS-Security Username Token [1] Links: 2013/8/30 Boris Staal [email protected]
|
Currently it parses that into |
0.8.3 released. Thanks. |
In Rails 4.0 running with Ruby 2.0 following instruction in readme file Users will get (and I did) "handle_inverified_request" error. It's obvious not an issue, it's just request were not signed with token, never less i suggest updating readme file with "protect_from_forgery except:....." filter.
One more thing...how do You do UsernameToken Authentication using wash_out?
The text was updated successfully, but these errors were encountered: