Skip to content
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

Add self-signed chain #32

Merged
merged 1 commit into from
Jan 31, 2017
Merged

Add self-signed chain #32

merged 1 commit into from
Jan 31, 2017

Conversation

andrewjamesbrown
Copy link
Contributor

Add self-signed chain methods to ensure that CI passes. Currently the self-signed chain simply returns nil; this could be enhanced later but works for now.

@andrewjamesbrown andrewjamesbrown force-pushed the master branch 4 times, most recently from 71f88b4 to ffab944 Compare January 21, 2017 03:50
Most java applications require both the certificate and the intermediate
chain to be part of the keystore; this adds the intermediate certificate
chain to support these apps.
@andrewjamesbrown
Copy link
Contributor Author

@zuazo it looks like only Travis is running CI... any suggestions on how to run the integration tests using Circle? I've run the modified ones on my machine (which pass), but running them all is a PITA. Thanks!

@zuazo
Copy link
Owner

zuazo commented Jan 22, 2017

I have enabled CircleCI builds on forked PRs. I didn't know it is disabled by default.

Anyway, Travis CI seem to be failing due to this issue:

ku1ik/rainbow#48

I tried re-running the job, but it's still not fixed.

After this is fixed, I'm going to try to run Circle CI on your branch locally.

@zuazo
Copy link
Owner

zuazo commented Jan 31, 2017

Merged! Thank you @andrewjamesbrown! 😃

@zuazo
Copy link
Owner

zuazo commented Feb 10, 2017

Released in 2.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants