Replies: 6 comments
|
Pull Request for Feature in Python library: langfuse/langfuse-python#1318 |
|
Thanks for opening this Github idea - @tw-dpd ! |
|
I'm very interested in this option. It is not uncommon for companies to have their own internal auth system and currently langfuse forces them to publicly expose deployments which otherwise could be internal only, or to settle for running no authz/rbac, which is a non-starter. |
|
Hi, we have the same interest to host langfuse inside an internal network on GCP. Really look forward to a proper solution to move this forward! |
|
Hi @frankcaoyun, i raised a feature request for this as Langfuse stated they had no interest from users in this and would not accept the PR |
|
Hey @tw-dpd thanks for the reply. The PR looks like it's introducing the additional IAP authentication layer that adds the complexity where original langfuse already support SSO. I was just looking for a solution for deployment in the internal company network on GCP with no app-side logic needs to be changed, perhaps that would be a smaller change to manage if possible. Anyways thanks for the reply! |
Uh oh!
There was an error while loading. Please reload this page.
Describe the feature or potential improvement
Support Dynamic Headers in Otel Traces and Langfuse API Calls
Additional information
Adding this feature would allow users to deploy Langfuse behind an authenticated proxy and not have to expose Langfuse to the public internet directly - significantly improving the security of a deployment and allowing additional customers to deploy that may have been put off by the thought of exposing a Langfuse instance in this way.
All reactions