You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traditionally, Shlink las only allowed managing API keys through its built-in CLI tool.
The reason was that exposing this, would introduce some security concerns. Keeping it in the CLI forces you to have physical access to the server.
However, even though nobody has ever asked for it, there are valid reasons to expose it, like an eventual external CLI for Shlink that interacts with a server via API.
Do you think Shlink should expose the API key creation through its REST API
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Traditionally, Shlink las only allowed managing API keys through its built-in CLI tool.
The reason was that exposing this, would introduce some security concerns. Keeping it in the CLI forces you to have physical access to the server.
However, even though nobody has ever asked for it, there are valid reasons to expose it, like an eventual external CLI for Shlink that interacts with a server via API.
8 votes ·
Beta Was this translation helpful? Give feedback.
All reactions