Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
1.1.0
-
None
-
None
Description
WIth all ssl values configured but ranger.service.https.attrib.keystore.keyalias having a value of an alias name that does not exist in the jks of the file referred to by ranger.https.attrib.keystore.file. Then run ranger-admin start, the process launches, no errors/exceptions BUT netstat -anp reveals no process listening on port 6182, curl/browser does not resolve for port 6182.
Purpose of this Jira is to make the ranger-admin process exit and print an exception whenever the tomcat webserver does not listen on 6182, rather than current behavior now where admin process stays running.
Attachments
Issue Links
- duplicates
-
RANGER-3695 Ranger Keystore alias should be configurable
- Patch Available