-
Notifications
You must be signed in to change notification settings - Fork 1.1k
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Configuration with KeyStore does not seem to work #387
Comments
Hmm, it looks like an oversight that the keyStore is not being transferred across from the But the fact that the KeyStore is not serializable may be a bigger problem. We need the KeyStore to be available in the SenderService so we need some way to send it to it. |
Thanks for your fast reply! Basically, I use a similar approach as Google describes it for constructing the KeyStore: http://developer.android.com/training/articles/security-ssl.html#UnknownCa Here is my code (the certificate is stored in my asset folder):
|
@svenfrauen Try the change that @F43nd1r has added to master. |
I think in this case |
This is awesome! I just tried the new master code changes and the configuration with |
All thanks go to @F43nd1r on this one :-) |
Hi,
I am using ACRA version 4.8.2 and want to connect it to my own Acralyzer backend via a self signed SSL certificate. Therefore, I am configuring a KeyStore with my self signed certificate and building the configuration:
However, it seems that the ACRA config does not set the custom KeyStore, as the new config does not include the KeyStore with my certificate. Apparently, the keyStore is not set in the ACRAConfiguration constructor: https://github.com/ACRA/acra/blob/master/src/main/java/org/acra/config/ACRAConfiguration.java#L114
Furthermore, if I try to set the KeyStore directly in the ACRAConfiguration, which is deprecated, I get an exception:
Is there any other way to set the self signed SSL certificate or is this a problem in ACRA?
Thanks for your time,
Sven!
The text was updated successfully, but these errors were encountered: