Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

用户目录逻辑删除会导致相同登陆域的目录不可创建 #441

Closed
abbyWJM opened this issue May 16, 2022 · 5 comments
Closed
Assignees
Labels
Priority: High Sign: feature requested New feature request Type: enhancement Enhancement for existing feature Type: proposal Proposal Type: question Usage or problems

Comments

@abbyWJM
Copy link

abbyWJM commented May 16, 2022

在实施过程中,客户习惯创建一个本地目录用于功能验证。在功能验证完毕后,需要正式对接ad或ldap时,本地目录的登录域会重复,在页面上删除该目录也无法解决此问题,目前解决方式为手动去数据库中清理对应的目录,或者直接重置用户管理saas的数据库。
基于此逻辑,也会衍生出一系列权限中心无法正常同步组织架构的问题。

@abbyWJM abbyWJM added Type: question Usage or problems Sign: feature requested New feature request labels May 31, 2022
@wklken wklken added Type: enhancement Enhancement for existing feature Type: proposal Proposal Priority: High labels Oct 12, 2022
@wklken
Copy link
Collaborator

wklken commented Oct 12, 2022

需要看下, 目前会引入很多问题, 带来很多排查

删除后, 不可见, 没有地方恢复会执行真删除, 导致软删除的目录占用了唯一字段

  1. 当用户新建一个目录存在重复唯一值时, 报错, 并且无解;
  2. 当用户新建一个目录, 配置了同一个ladp源, 点击同步, 同步会失败, 无解

需要考虑:

  1. 怎么展示
  2. 可以恢复软删除目录及其用户
  3. 可以执行真删除

@wklken wklken pinned this issue Oct 12, 2022
@wklken
Copy link
Collaborator

wklken commented Oct 13, 2022

或者, 点击删除目录, 直接物理删除目录+目录下用户?
风险: 误删除无法恢复

@wklken
Copy link
Collaborator

wklken commented Oct 20, 2022

image

@wklken
Copy link
Collaborator

wklken commented Oct 20, 2022

@Shutulee @Xmandon 这里目前导致了很多问题排查(原因, 被删除目录没有真正删除, 占坑导致后续新增目录/新增同步数据报错)

看看产品设计上能不能先处理下, 避免用户进入这种场景

  1. 要么原先删除直接就是硬删除
  2. 要么软删除之后能在列表中看到, 能恢复, 也能硬删除

@wklken
Copy link
Collaborator

wklken commented Nov 10, 2022

close, #760 fixed this

@wklken wklken closed this as completed Nov 10, 2022
@wklken wklken unpinned this issue Nov 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High Sign: feature requested New feature request Type: enhancement Enhancement for existing feature Type: proposal Proposal Type: question Usage or problems
Projects
None yet
Development

No branches or pull requests

3 participants