fzhsbc opened a new issue, #18277: URL: https://github.com/apache/dolphinscheduler/issues/18277
# [Improvement][Docs] Clarify tenant boundary and task runtime credentials Some deployments run DolphinScheduler tasks that need to access external data platforms, object stores, or catalogs with short-lived credentials. In those environments, the DolphinScheduler tenant is often an execution resource boundary, such as the OS user used by the Worker to run a process, while data authorization is enforced by the external data system. The current security documentation already explains that tenants map to Linux users. It would be helpful to make the boundary explicit and add task-plugin guidance for runtime credentials: - A tenant should not be treated as a fine-grained data permission principal by itself. - Long-lived external credentials should not be stored in task definitions or printed in logs. - Task plugins that fetch runtime credentials should bind them to task context, such as project, workflow, task instance, datasource, tenant, and worker group, and clean up temporary files after execution. - External data systems remain responsible for validating and enforcing data permissions. This issue is documentation-scoped. It does not propose changing DolphinScheduler's current authorization model in this PR. A future feature discussion could separately consider a core runtime credential provider hook. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
