apache / apache/incubator-seata
seata如何保证客户端与服务端的安全RPC连接和授权
Open
- Dominant language
- Java
- Stars
- 26k
- Forks
- 8.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 4
Description
好像代码没有看到关于通讯的加密还有授权的模块,在安全审核的要求严格,这个功能是生产环境的硬规定。
请问这个功能会开发吗?还是现在版本可以通过配置或者一些第三方的security provider就可以接入
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the existing client/server RPC configuration and checking whether encryption, authorization, or security-provider integration is documented. Done would be a concrete decision and documented configuration or an explicitly scoped implementation for the production security requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100