You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "gaopeng666 (via GitHub)" <gi...@apache.org> on 2023/08/25 02:00:20 UTC
[GitHub] [dolphinscheduler] gaopeng666 opened a new issue, #14811: [Bug] [api] When using Casdoor SSO, ldap, OAuth2 to log in, the tenant of the currently logged in user is not specified
gaopeng666 opened a new issue, #14811:
URL: https://github.com/apache/dolphinscheduler/issues/14811
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When using Casdoor SSO, ldap, or OAuth2 to log in, if the user is logging in for the first time, the tenant is not specified when creating a new user in the t_ds_user table, and the default is 0. When logging in, the tenant will be checked when the resource interface is obtained, and the tenant of the current login user is not specified. question
### What you expected to happen
### How to reproduce
using Casdoor SSO, ldap, or OAuth2 to log in
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] 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.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14811: [Bug] [api] When using Casdoor SSO, ldap, OAuth2 to log in, the tenant of the currently logged in user is not specified
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #14811:
URL: https://github.com/apache/dolphinscheduler/issues/14811#issuecomment-1692647736
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues.
### What happened
When using Casdoor SSO, ldap, or OAuth2 to log in, if the user is logging in for the first time, the tenant is not specified when creating a new user in the t_ds_user table, and the default is 0. When logging in, the tenant will be checked when the resource interface is obtained, and the tenant of the current login user is not specified. question
### What you expected to happen
### How to reproduce
using Casdoor SSO, ldap, or OAuth2 to log in
### Anything else
_No response_
### Version
dev
### Are you willing to submit PR?
- [X] 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] ruanwenjun closed issue #14811: [Bug] [api] When using Casdoor SSO, ldap, OAuth2 to log in, the tenant of the currently logged in user is not specified
Posted by "ruanwenjun (via GitHub)" <gi...@apache.org>.
ruanwenjun closed issue #14811: [Bug] [api] When using Casdoor SSO, ldap, OAuth2 to log in, the tenant of the currently logged in user is not specified
URL: https://github.com/apache/dolphinscheduler/issues/14811
--
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