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

Graphd need support SSL/TLS #1848

Closed
knightXun opened this issue Mar 2, 2020 · 2 comments
Closed

Graphd need support SSL/TLS #1848

knightXun opened this issue Mar 2, 2020 · 2 comments
Labels
duplicate Solution: this issue or pull request already exists

Comments

@knightXun
Copy link
Contributor

Connecting to Graphd is not secure. Graphd need support ssl or tls connection. Please support this in rc4

@knightXun knightXun added the priority/unbreak-pri Priority: unbreak now!!! label Mar 2, 2020
@jude-zhu jude-zhu added this to the R201910_RC4 milestone Mar 3, 2020
@panda-sheep
Copy link
Contributor

First, LDAP supports TLS, which means that communication between graphd and the LDAP server is encrypted using TLS

Here The SSL / TLS is only console and graphd, or graph clinet and graph server, meta client and meta server, storage client and storage server communicate using SSL / TLS encrypted

@jude-zhu jude-zhu removed the priority/unbreak-pri Priority: unbreak now!!! label Mar 3, 2020
@jude-zhu jude-zhu removed this from the R201910_RC4 milestone Mar 3, 2020
@CPWstatic
Copy link
Contributor

We had a plan to implement it in this quarter, please track it with #2584

@CPWstatic CPWstatic added the duplicate Solution: this issue or pull request already exists label Aug 27, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Jan 31, 2023
…soft-inc#1848)

* optimize left join predicate & Eliminate useless appendVertices

* fix

* update

* address leftExprs&rightExprs

* address comments

Co-authored-by: jie.wang <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Solution: this issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants