-
-
Notifications
You must be signed in to change notification settings - Fork 920
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
Krypt error when Rails 4 run in production mode on a Java Application Server #1018
Comments
No, I think it's not a duplicate. I fix the PKCS5 error with
But's it's a jruby-openssl error which is not required with Rails 4 secret_key_base. When I have the krypt error I haven't jruby-openssl in my Gemfile. It is not used. |
@pierrickrouxel Thanks for the detailed explanation. |
What JRuby version is this? |
1.7.4 but I haven't try with another version ! |
@BanzaiMan Yes, I'll try to fix this! @pierrickrouxel Which application server are you using? |
FWIW JRuby 1.7.5 will ship with jruby-openssl and krypt* as default gems,
|
I use Websphere Application Server but the bug appears with warbler Jetty embedded server too. Thank you for your job ! |
Hi Pierrick, Have you finally found a way to solve your issue ? Thanks |
No I haven' t found solution. I use rails 3 way for moment. |
OK, thanks 2013/10/13 Pierrick Rouxel notifications@github.com
|
@pierrickrouxel This never occurs with Rails 3, only with 4, right? I'll try to reproduce it with Jetty as you confirmed it appears there, too. You wouldn't happen to have a proof of concept that I could use for hunting down the error? That would be awesome! |
Good morning guys, I just wrote a simple application with TorqueBox and Krypt to reproduce the environment and the issue mentioned https://github.com/abstractj/torquebox-krypt-example I've also introduced the secret token https://github.com/abstractj/torquebox-krypt-example/blob/master/config/initializers/secret_token.rb#L12. Maybe this is neither an issue related with JRuby nor Krypt? |
Hi,
I have an error with krypt when I use the new Rails 4 secret token mode :
instead of
Application raise SOMETIMES this error :
Due to this error Rails 4 it's absolutelly unusable with this secret_token generation.
The issue is possible to reduce with an executable jar built with warbler.
For people who experienced the same problem the temporary solution is :
Rails 4 requires krypt only if secret_key_base is used
gem 'jruby-openssl', :require => false
to your GemfileIssue is open in krypt project too : krypt/krypt#38
The text was updated successfully, but these errors were encountered: