JanusGraph / JanusGraph/janusgraph-visualizer
Support for SASL_SSL with janusgraph-visualizer
- Dominant language
- JavaScript
- Stars
- 42
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Hi JanusGraph Community,
First, I want to express my gratitude for the incredible work on JanusGraph and its ecosystem. The tool has been instrumental for us, and I greatly appreciate the effort and dedication of everyone involved.
I am currently running JanusGraph with SASL configuration for WebSocket authentication. To enhance security, I am transitioning to use SASL_SSL by adding the necessary SSL configuration. However, I have encountered some challenges with the JanusGraph-Visualizer client, as it seems there are no options to configure SSL support.
Here are my questions and concerns:
**Connecting with SSL:** Is there a way to connect JanusGraph-Visualizer to a JanusGraph server that has both WebSocket authentication and SSL enabled?
**Feature Availability:** If this is not currently supported, are there any plans to add support for SSL connections on top of SASL in JanusGraph-Visualizer in the future?
**Best Practices or Alternatives:** Are there any recommendations or alternative approaches to enable Authentication and SSL for clients interacting with a JanusGraph server in this setup?
I hope this aligns with the community’s roadmap or sparks a discussion about its feasibility. If there is a way I can contribute to this feature (documentation, testing, etc.), I would be happy to assist.
Thank you for taking the time to consider this request, and I look forward to hearing your thoughts!
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by tracing how janusgraph-visualizer configures its WebSocket connection and handles existing SASL authentication, then determine whether SSL settings can be supplied. Done means establishing whether SASL_SSL is supported and, if not, defining and validating a concrete client-side change or documenting the supported alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100