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

Enabling additional configuration parameters for HTTPS #167

Closed
nevenr opened this Issue Oct 21, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@nevenr
Contributor

nevenr commented Oct 21, 2014

It would be nice to have additional configuration parameters for HTTPS like:

  • secureSocketProtocol
  • keyStoreType
  • keyManagerAlgorithm
  • trustManagerAlgorithm
    so it would be possible to configure jolokia inline with security requirements.

nevenr added a commit to nevenr/jolokia that referenced this issue Oct 21, 2014

Documentation update for:
- JVM Agent and SSL client authentication does not work rhuss#166
- Enabling additional configuration parameters for HTTPS rhuss#167
@nevenr

This comment has been minimized.

Contributor

nevenr commented Oct 21, 2014

Feature added. Supported supplying parameters through configuration properties file, agent parameters and attaching on the fly parameters.
Commits:
nevenr@8a2c787
nevenr@b09f4b6
nevenr@53cf028
nevenr@3350aef

@nevenr nevenr closed this Oct 21, 2014

@nevenr nevenr reopened this Oct 29, 2014

@nevenr

This comment has been minimized.

Contributor

nevenr commented Oct 29, 2014

Please add milestone 1.3.0 and assign to me.
Thanks,
N.

@rhuss rhuss added this to the 1.3.0 milestone Nov 8, 2014

rhuss added a commit that referenced this issue Nov 8, 2014

Documentation update for:
- JVM Agent and SSL client authentication does not work #166
- Enabling additional configuration parameters for HTTPS #167
@rhuss

This comment has been minimized.

Owner

rhuss commented Nov 9, 2014

Jolokia 1.2.3 (not 1.3.0) is released and contains your fixes. Thanks a lot !

@rhuss rhuss closed this Nov 9, 2014

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