• L
    [Fix-10181] Fix the logic of judging that the tenant does not exist (#10185) · a0771541
    lugela 提交于
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    The configuration item adds 'tenant-distributed-user' in worker application.yaml to make it suitable for distributed users. If it is false, the original logic remains unchanged.
    
    At present, considering that it is a distributed user, it should not be allowed to create users in linux
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Add test method
    
    The configuration item adds 'tenant-distributed-user' in worker application.yaml to make it suitable for distributed users. If it is false, the original logic remains unchanged.
    
    At present, considering that it is a distributed user, it should not be allowed to create users in linux
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Add parameter description to configuration.md
    
    Add test method
    
    The configuration item adds 'tenant-distributed-user' in worker application.yaml to make it suitable for distributed users. If it is false, the original logic remains unchanged.
    
    At present, considering that it is a distributed user, it should not be allowed to create users in linux
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Add parameter description to configuration.md
    
    Add test method
    
    The configuration item adds 'tenant-distributed-user' in worker application.yaml to make it suitable for distributed users. If it is false, the original logic remains unchanged.
    
    At present, considering that it is a distributed user, it should not be allowed to create users in linux
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    
    * [Fix-10181] Fix the logic of judging that the tenant does not exist
    
    Add parameter description to configuration.md
    
    Add test method
    
    The configuration item adds 'tenant-distributed-user' in worker application.yaml to make it suitable for distributed users. If it is false, the original logic remains unchanged.
    
    At present, considering that it is a distributed user, it should not be allowed to create users in linux
    
    Use the linux command as id to get the user information that exists in /etc/passwd file and the cached sssd user.
    for example:
    id test
    1. exist in /etc/passwd file or ldap :  uid=1030(test) gid=1030(test) groups=1030(test)
    2. no exist  in /etc/passwd file and ldap: id: test: no such user
    
    Temporarily unable to test the system for windows and mac
    Co-authored-by: Nouyangl <ouyangl@tebon.com.cn>
    a0771541
OSUtils.java 14.7 KB