[ 
https://issues.apache.org/jira/browse/DUBBO-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shengli Cao updated DUBBO-39:
-----------------------------
    Description: 
Currently the security support of Dubbo is not enough. We should provide more 
feature to use. Such as TLS support,  Authorization,high-level encrypt data.

*Required feature*

1.  TLS support 

1.1 Support TLS , maybe you can refer the netty implements.

1.2 Use the same port as the TCP port , default is 20880.  And the server 
should consume the invocation of simple TCP or TCP+TLS.

 

*Options feature*

2.  Authorization

2.1  You can add some authorization between client and server.

2.2  You should focus on client and server communication, but not on 
registration.

2.3  This feature is option. 

  was:
Currently the security support of Dubbo is not enough. We should provide more 
feature to use. Such as TLS support,  Authorization,high-level encrypt data.

*Required feature*

1.  TLS support 

1.1 Support TLS , maybe you can refer the netty implements.

1.2 Use the same port as the TCP port , default is 20880.  And the server 
should consume the invocation of simple TCP or TCP+TLS.

 

*Options feature*

*2.*  Authorization

*2.1  You can add some authorization between client and server.*

*2.2  You should focus on client and server communication, but not on 
registration.*

*2.3  This feature is option.* 


> Support more security choose 
> -----------------------------
>
>                 Key: DUBBO-39
>                 URL: https://issues.apache.org/jira/browse/DUBBO-39
>             Project: Apache Dubbo
>          Issue Type: New Feature
>            Reporter: Shengli Cao
>            Priority: Major
>              Labels: ASoC2019
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> Currently the security support of Dubbo is not enough. We should provide more 
> feature to use. Such as TLS support,  Authorization,high-level encrypt data.
> *Required feature*
> 1.  TLS support 
> 1.1 Support TLS , maybe you can refer the netty implements.
> 1.2 Use the same port as the TCP port , default is 20880.  And the server 
> should consume the invocation of simple TCP or TCP+TLS.
>  
> *Options feature*
> 2.  Authorization
> 2.1  You can add some authorization between client and server.
> 2.2  You should focus on client and server communication, but not on 
> registration.
> 2.3  This feature is option. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to