Details
-
Sub-task
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
None
-
None
-
None
-
Reviewed
Description
When security is enabled, ozone services should not start up, even if ozone configurations are enabled. This is important to ensure a user experimenting with ozone doesn't inadvertently get exposed to attacks. Specifically,
1) KSM should not start up.
2) SCM should not startup.
3) Datanode's ozone xceiverserver should not startup, and must not listen on a port.
4) Datanode's ozone handler port should not be open, and webservice must stay disabled.
Attachments
Attachments
Issue Links
- links to