API Password #266

New Issue

GiteaMirror · 2025-11-09T09:44:29-06:00

GiteaMirror commented

2025-11-09 09:44:29 -06:00

Originally created by @loudotdigital on GitHub (May 3, 2024).

Describe the feature you'd like to see
Ability to set a password in an environment variable file (e.g., .env) and send it in the headers of API requests

Describe alternatives you've considered
Using API tokens or keys instead of passwords.

Additional context
This feature would allow developers to store a API password securely in an environment variable file and send it in the headers of API requests for authentication. It would provide a simple and straightforward way to protect API access without relying on external authentication providers or platform-specific mechanisms.

Originally created by @loudotdigital on GitHub (May 3, 2024). **Describe the feature you'd like to see** Ability to set a password in an environment variable file (e.g., .env) and send it in the headers of API requests **Describe alternatives you've considered** Using API tokens or keys instead of passwords. **Additional context** This feature would allow developers to store a API password securely in an environment variable file and send it in the headers of API requests for authentication. It would provide a simple and straightforward way to protect API access without relying on external authentication providers or platform-specific mechanisms.

GiteaMirror added the feature request label 2025-11-09 09:44:29 -06:00

GiteaMirror closed this issue

2025-11-09 09:44:29 -06:00

GiteaMirror commented

2025-11-09 09:44:30 -06:00

@lostdusty commented on GitHub (May 3, 2024):

chatgpt ass issue

@lostdusty commented on GitHub (May 3, 2024): chatgpt ass issue

GiteaMirror commented

2025-11-09 09:44:30 -06:00

@loudotdigital commented on GitHub (May 3, 2024):

chatgpt ass issue

please, educate me

@loudotdigital commented on GitHub (May 3, 2024): > chatgpt ass issue please, educate me

GiteaMirror commented

2025-11-09 09:44:30 -06:00

@ethrydevelops commented on GitHub (May 11, 2024):

you do realise that the web part.. has to talk to the api, right? and for it to do that, it has to expose the password to the user, right?

and also, why are you even trying to password protect your instance?

@ethrydevelops commented on GitHub (May 11, 2024): you do realise that the web part.. has to talk to the api, right? and for it to do that, it has to expose the password to the user, right? and also, why are you even trying to password protect your instance?

GiteaMirror commented

2025-11-09 09:44:30 -06:00

@loudotdigital commented on GitHub (May 20, 2024):

you do realise that the web part.. has to talk to the api, right? and for it to do that, it has to expose the password to the user, right?

and also, why are you even trying to password protect your instance?

the way I see it I can use my instance only to receive API calls, that wont be made via "the web part", and obviously I wanted to password protect it so it doenst have unauthorized calls

@loudotdigital commented on GitHub (May 20, 2024): > you do realise that the web part.. has to talk to the api, right? and for it to do that, it has to expose the password to the user, right? > > and also, why are you even trying to password protect your instance? the way I see it I can use my instance only to receive API calls, that wont be made via "the web part", and obviously I wanted to password protect it so it doenst have unauthorized calls

GiteaMirror commented

2025-11-09 09:44:30 -06:00

@dumbmoron commented on GitHub (May 29, 2025):

this is done now via api keys, just forgot to close this issue

@dumbmoron commented on GitHub (May 29, 2025): this is done now via api keys, just forgot to close this issue