[GitHub] [dolphinscheduler] huagetai opened a new issue #9152: [Feature][Multi-tenancy] Shouldn't all operations related to user authorization be restricted to the same tenant?

[GitBox <gi...@apache.org>]

huagetai opened a new issue #9152:
URL: https://github.com/apache/dolphinscheduler/issues/9152


   ### Search before asking
   
   - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
   
   
   ### Description
   
   Shouldn't all operations related to user authorization be restricted to the same tenant?
   For example: project authorization, alarm group authorization, resource authorization, etc.
   The current design can authorize users across multiple tenants.Tenants are effectively replaced by users.
   
   ### Use case
   
   Isolation of projects, resources, data sources, work groups, etc. through tenants
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #9152: [Feature][Multi-tenancy] Shouldn't all operations related to user authorization be restricted to the same tenant?

[GitBox <gi...@apache.org>]

github-actions[bot] commented on issue #9152:
URL: https://github.com/apache/dolphinscheduler/issues/9152#issuecomment-1077298219


   Hi:
   * Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
   * In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
   * If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/en-us/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.


-- 
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: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org