Skip to content

Best practices in authenticating who can start the gradio launched via frp #23

@erikdao

Description

@erikdao

Context

  • I followed the instructions in README and setup the frps and deploy it on our GCP infra as a VM, with public IP and a domain mapped to that IP
  • The gradio.launch(shared=True, share_server_address="myfrpsdomain.com:7000") works as expected.
  • But as far as I understand, anyone on the internet can use my shared server.

Question

  • What is the best way to authenticate/restrict so that only certain user (e.g., people inside my team) can launch gradio apps via my frps?
  • A possible solution is to restrict on a network level, e.g., only services/users within some VPC in my GCP can connect to this shared server. However, that comes with limitations: we have apps and services outside of our GCP (on huggingface, and other places) that want to connect to the frps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions