Closed kouzant closed 6 years ago
[HOPSWORKS-542] Add REST endpoint for revoking application certificates and refactor signing csr
[HOPSWORKS-542] Comment-out adding crypto material as local resources for Spark
[HOPSWORKS-542] Remove adding user's crypto material as local resources of a container if Hops RPC TLS is enabled
[HOPSWORKS-542] Fix bug in Jupyter config generator with Spark local resources list
[HOPSWORKS-542] Change the authentication mechanism with user submitted keystore
Please check if the PR meets the following requirements
[x] Adds tests for the submitted changes (for bug fixes & features)
[x] Passes the tests
[x] HOPSWORKS JIRA issue has been opened for this PR
[x] All commits have been squashed down to a single commit
Post a link to the associated JIRA issue https://hopshadoop.atlassian.net/browse/HOPSWORKS-542
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
[HOPSWORKS-542] Add REST endpoint for revoking application certificates and refactor signing csr
[HOPSWORKS-542] Comment-out adding crypto material as local resources for Spark
[HOPSWORKS-542] Remove adding user's crypto material as local resources of a container if Hops RPC TLS is enabled
[HOPSWORKS-542] Fix bug in Jupyter config generator with Spark local resources list
[HOPSWORKS-542] Change the authentication mechanism with user submitted keystore
Make sure there is no duplicate PR for this issue
Please check if the PR meets the following requirements
[x] Adds tests for the submitted changes (for bug fixes & features)
[x] Passes the tests
[x] HOPSWORKS JIRA issue has been opened for this PR
[x] All commits have been squashed down to a single commit
Post a link to the associated JIRA issue https://hopshadoop.atlassian.net/browse/HOPSWORKS-542
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: