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

[优化] 同步失败没有详细日志, 需要到后台看 #424

Closed
wklken opened this issue May 11, 2022 · 2 comments
Closed

[优化] 同步失败没有详细日志, 需要到后台看 #424

wklken opened this issue May 11, 2022 · 2 comments
Assignees
Labels
Layer: api Api module related Type: enhancement Enhancement for existing feature Type: proposal Proposal
Milestone

Comments

@wklken
Copy link
Collaborator

wklken commented May 11, 2022

域名不可用/接口错误/状态非 200 等场景, 都无法看到报错日志

如果可以, 脱敏后展示最好, 避免查日志

@wklken wklken added Type: enhancement Enhancement for existing feature Layer: api Api module related Type: proposal Proposal labels May 11, 2022
@wklken wklken self-assigned this May 11, 2022
@wklken
Copy link
Collaborator Author

wklken commented May 12, 2022

背景: ldap测试连接失败, 无法看到详情

运维建议:

  1. 字段填写错误.
  2. ldap连接失败: 连接被拒绝/超时等网络层的报错.
  3. ldap协议层的报错: 协议不匹配, 服务端不兼容.
  4. ldap认证失败.
  5. ldap拓扑拉取失败.

升级ldap3到 2.7 解决 (#428 )

问题点: ldap3很多bug和错误, 返回的是相同的Error, 无法根据ldap3的异常, 进一步判断具体问题


另外, ldap由于是外部插件的形式, 内部根本没有场景, 而且ldap server多种多样, 配置差异很大, 非常不好配置; 应该同服务商一起, 整一份ldap的配置文档? 按照ldap server及对应的场景;

@wklken wklken added this to the Y2022M20-21 milestone May 16, 2022
@wklken
Copy link
Collaborator Author

wklken commented May 17, 2022

#435
#445

将ldap3的原始异常信息暴露到前端给到用户, 包括但不限于:invalid server address / Network Error等等, 并且包含ldap3的具体异常类型 https://ldap3.readthedocs.io/en/latest/exceptions.html


开发者可以很直观根据错误类型确定问题

close, 收集一波用户的异常整理到文档, 后续再根据提示, 区分类型, 提示更多的信息给到开发者

@wklken wklken closed this as completed May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Layer: api Api module related Type: enhancement Enhancement for existing feature Type: proposal Proposal
Projects
None yet
Development

No branches or pull requests

1 participant