Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃挕 Add option to require Cloudflare Access #1169

Closed
mhr3 opened this issue Jan 30, 2024 · 2 comments
Closed

馃挕 Add option to require Cloudflare Access #1169

mhr3 opened this issue Jan 30, 2024 · 2 comments
Labels
Priority: Normal Minor issue impacting one or more users Type: Feature Request A big idea that would be split into smaller pieces

Comments

@mhr3
Copy link

mhr3 commented Jan 30, 2024

Describe the feature you'd like
When mapping services to domains in the configuration, it would be useful it you could specify that a service requires authentication via Cloudflare Access. This would ensure that when there's no Access application setup (inadvertently), the service isn't publicly accessible on the internet (as that would be the case atm if the tunnel is already mapped to a dns name).

Something along the lines of:

  - hostname: gitlab.widgetcorp.tech
    service: http://localhost:80
    requires_auth: true
@mhr3 mhr3 added Priority: Normal Minor issue impacting one or more users Type: Feature Request A big idea that would be split into smaller pieces labels Jan 30, 2024
@Erisa
Copy link

Erisa commented Jan 30, 2024

You can use these: https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/configure-tunnels/origin-configuration/#access-settings

  - hostname: gitlab.widgetcorp.tech
    service: http://localhost:80
    requires_auth: true
    access:
      required: true
      teamName: <your-team-name>
      audTag:
        - aud1 <Access-application-audience-tag>
        - aud2 <Optional-additional-tags>

If you don't have a specific Access app to tie it to, just omit the audTag part and it will work with any application.

@joliveirinha
Copy link
Contributor

as stated, this is already supported as suggested by @Erisa

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Normal Minor issue impacting one or more users Type: Feature Request A big idea that would be split into smaller pieces
Projects
None yet
Development

No branches or pull requests

3 participants