https://github.com/ghepes/info-cloudflare-zero-trust
info to add worker for zero trust
https://github.com/ghepes/info-cloudflare-zero-trust
app cloudflare-workers html login-security trust zero zero-trust-network-access
Last synced: 9 months ago
JSON representation
info to add worker for zero trust
- Host: GitHub
- URL: https://github.com/ghepes/info-cloudflare-zero-trust
- Owner: Ghepes
- License: mit
- Created: 2025-07-31T10:48:29.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-08-09T20:17:24.000Z (10 months ago)
- Last Synced: 2025-08-09T22:04:59.582Z (10 months ago)
- Topics: app, cloudflare-workers, html, login-security, trust, zero, zero-trust-network-access
- Language: JavaScript
- Homepage: https://github.com/Ghepes/info-cloudflare-zero-trust.git
- Size: 37.1 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Secure proxy .env
This is a Cloudflare Worker with Secure proxy .ENV
This is an example project made to be used as a quick start into building .ENV
secure proxy.
## Get started
1. Sign up for [Cloudflare Workers](https://workers.dev). The free tier is more than enough for most use cases.
2. Clone this project and install dependencies with `npm install`
3. Run `wrangler login` to login to your Cloudflare account in wrangler
4. Run `wrangler deploy` to publish the .ENV secure proxy to Cloudflare Workers
## Project structure
1. Your main router is defined in `src/index.js`.
* The 'fetch' handler is the main entry point of the Worker.
* Processes incoming HTTP requests to the HTML webapp.
* {Request} request HTTP Worker request.
* {Object} env The object containing the environment variables (including secrets).
* {ExecutionContext} ctx The execution context of the request.
* These are taken from the secrets you added with `wrangler secret put`.
* Make sure you define them as CF_ACCESS_CLIENT_ID and CF_ACCESS_CLIENT_SECRET.
* newRequest.headers.set('CF-Access-Client-Id', env.CF_ACCESS_CLIENT_ID);
* newRequest.headers.set('CF-Access-Client-Secret', env.CF_ACCESS_CLIENT_SECRET);
## Development
1. Run `wrangler dev` to start a local instance of the API.
2. Open `http://localhost:8787/` in your browser to see the Swagger interface where you can try the endpoints.
3. Changes made in the `src/` folder will automatically trigger the server to reload, you only need to refresh the Swagger interface.
## Worker deploy
### command is used to link a Cloudflare account with the Wrangler CLI
wrangler connect --account
3. Run `wrangler login` to login to your Cloudflare account in wrangler
4. Run `wrangler deploy` to publish the .ENV secure proxy to Cloudflare Workers
wrangler deploy .
add manual secret value to the worker cloudflare
CF_ACCESS_CLIENT_ID=CF-Access-Client-Id: 22xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.access
CF_ACCESS_CLIENT_SECRET=CF-Access-Client-Secret: f20xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx