plotly / plotly/dash-auth

Is it possible to do <username>:<password> in URL for dash-auth basic http authentication?

Open
#112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
135
Forks
67
PR merge metrics
No merged PRs in 30d

Description

I came across this in the test code which leads me to believe it is not, but wondering if there is any update on when dash routes might support this or if there is another way around it (besides reloading the URL again).

Currently behavior is page returns "Loading..." to the browser and I see this from the server (before reloading):

$ python3 test_dash_auth.py
http://hello:wor:ld@barolo:47125
Dash is running on http://barolo:47125/

 * Serving Flask app "test_dash_auth" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: off
 * Running on http://barolo:47125/ (Press CTRL+C to quit)
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET / HTTP/1.1" 401 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET / HTTP/1.1" 200 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /assets/bWLwgP.css?m=1601518562.6601 HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/polyfill@7.v1_8_2m1601187996.8.7.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react-dom@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/prop-types@15.v1_8_2m1601187996.7.2.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_html_components/dash_html_components.v1_1_1m1599668561.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components.v1_12_1m1600343520.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components-shared.v1_12_1m1600343520.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/dash_renderer.v1_8_2m1601187996.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/react-dom@16.v1_8_2m1601187996.13.0.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/prop-types@15.v1_8_2m1601187996.7.2.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_html_components/dash_html_components.v1_1_1m1599668561.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components.v1_12_1m1600343520.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_core_components/dash_core_components-shared.v1_12_1m1600343520.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /_dash-component-suites/dash_renderer/dash_renderer.v1_8_2m1601187996.min.js HTTP/1.1" 403 -
192.168.0.186 - - [30/Sep/2020 21:15:35] "GET /assets/favicon.ico?m=1601263521.8334005 HTTP/1.1" 403 -

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with tests/test_basic_auth_integration.py at the referenced line and reproduce the URL containing username and password. Trace how the Dash routes and assets respond to the initial 401 and subsequent requests. Done means determining whether this URL form can work reliably, with implementation and tests if supported or a documented alternative if not.

Written by the indexing model from the issue text.

Assessment

Tech stack
flask, python
Domain
authentication, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.