You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Even through Nebula Graph is configured with no database password, the login page is shown. Developers must login with graphd <TAB> root <TAB> 1234 several times per day.
This also means the Studio cannot be easily configured to be integrated into other apps via <iframe> for quick access - users would have to login into each iframe.
Describe the solution you'd like
Have some setting that, when set, automatically logs in all browser visitors to the specified user/password/graphd. Make the setting dangerous-sounding, to ward off any production use.
For example, environment variables STUDIO_X_INSECURE_SKIP_AUTH=trueSTUDIO_X_INSECURE_SKIP_AUTH_USER=rootSTUDIO_X_INSECURE_SKIP_AUTH_PASS=1234STUDIO_X_INSECURE_GRAPHD=http://graphd:1234.
The developer would then be responsible for securing the access.
Describe alternatives you've considered
Additional context
Nebula Graph 3.6.0 , nebula-graph-studio:v3.9.1
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Even through Nebula Graph is configured with no database password, the login page is shown. Developers must login with
graphd <TAB> root <TAB> 1234
several times per day.This also means the Studio cannot be easily configured to be integrated into other apps via
<iframe>
for quick access - users would have to login into each iframe.Describe the solution you'd like
Have some setting that, when set, automatically logs in all browser visitors to the specified user/password/graphd. Make the setting dangerous-sounding, to ward off any production use.
For example, environment variables
STUDIO_X_INSECURE_SKIP_AUTH=true
STUDIO_X_INSECURE_SKIP_AUTH_USER=root
STUDIO_X_INSECURE_SKIP_AUTH_PASS=1234
STUDIO_X_INSECURE_GRAPHD=http://graphd:1234
.The developer would then be responsible for securing the access.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: