anyone can show view page source and see the URL and can access it without authentication so I need to make it secure and don’t show the URL that published from bokeh server
This Bokeh app below served by a Bokeh server that has been embedded
in another web app framework. For more information see the section
in the User's Guide.
You’ll need to run the bokeh server behind some kind of authenticating proxy, e.g Nginx is one possibility. There are still some open issues about various improvements that might be added to bokeh itself, e.g
anyone can show view page source and see the URL and can access it without authentication so I need to make it secure and don’t show the URL that published from bokeh server
This Bokeh app below served by a Bokeh server that has been embedded
in another web app framework. For more information see the section
in the User's Guide.
{{ script|safe }}
``
–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Is there any way for authentication in bokeh server I see an old document for authentication users by switching from single user to multi user by using -m but in the new versions there is no parameters call -m or mult users or any document about
Is it work now or no ?
···
On Tue, Jul 17, 2018 at 4:25 PM Bryan Van de ven [email protected] wrote:
You’ll need to run the bokeh server behind some kind of authenticating proxy, e.g Nginx is one possibility. There are still some open issues about various improvements that might be added to bokeh itself, e.g
anyone can show view page source and see the URL and can access it without authentication so I need to make it secure and don’t show the URL that published from bokeh server
This Bokeh app below served by a Bokeh server that has been embedded
in another web app framework. For more information see the section
in the User's Guide.
{{ script|safe }}
``
–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
That “-m” option refers to the old “bokeh-server”, which is long, long, long gone. The current generation Bokeh server is completely agnostic with respect to auth. There are simply too many options and possibilities, and we don’t have the resources or experience make them work. Instead of trying to re-inventing the wheel (badly and incompletely), that other tools already excel at, we made Bokeh flexible and integratable. As I stated earlier if you need auth, you will want to run behind a proxy that takes care of the auth.
Alternatively, you can work on (or wait for) the issue I linked to expose tornado’s “auth hook” in a reasonable way.
Is there any way for authentication in bokeh server I see an old document for authentication users by switching from single user to multi user by using -m but in the new versions there is no parameters call -m or mult users or any document about
Is it work now or no ?
On Tue, Jul 17, 2018 at 4:25 PM Bryan Van de ven [email protected] wrote:
You’ll need to run the bokeh server behind some kind of authenticating proxy, e.g Nginx is one possibility. There are still some open issues about various improvements that might be added to bokeh itself, e.g
anyone can show view page source and see the URL and can access it without authentication so I need to make it secure and don’t show the URL that published from bokeh server
This Bokeh app below served by a Bokeh server that has been embedded
in another web app framework. For more information see the section
in the User's Guide.
{{ script|safe }}
``
–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].