|
Wojciech Kapcia opened 4 years ago
|
||||||
|
|
Wojciech Kapcia batch edited 9 months ago
|
||||||
|
|
Wojciech Kapcia added "Related" #142 9 months ago
|
||||||
|
|
@andrzej.wojcik do we (still) need it? I think the initial idea was to provide a way to easily bootstrap Tigase and allow automatic configuration via REST but given that TheProject works I'm not sure it's still needed (maybe it uses "open_access")? If still needed, I assume the env-variable API key would be a global one (regexp for |
||||||
|
TheProject uses "open_access" as access to this API is forwarded through the proxy that requires authentication and due to that API key was not needed. Having an option to be able to "bootstrap" API key(s) from the env-variable, would be a desirable thing for deployment in which access to REST API is not guarded by any proxy. |
||||||
|
Referenced from commit 8 months ago
|
|||||||
|
|
Wojciech Kapcia changed state to 'In Progress' 8 months ago
|
||||||
|
|
Wojciech Kapcia changed state to 'In QA' 8 months ago
|
||||||
|
|
Added support for documentation: https://docs.tigase.net/projects/tigase-tigase-http-api/en/latest/Administration/tigase-http-api-release-notes.html#api-keys |
||||||
|
|
Wojciech Kapcia changed state to 'Closed' 8 months ago
|
| Type |
Task
|
| Priority |
Normal
|
| Assignee | |
| Version |
tigase-server-8.4.0
|
-
tigase-server-8.4.0 Closed
In some cases being able to configure installation via environment variables is desired (kan)