Andreas Grub
Currently, the API Key Id is a randomly generated UUID, which is not very human-readable.
When used in external systems, one could consider deriving a prefix such as
some-api-key
from the name "Some API key" by lowercasing it and replacing all chars not matching
[a-z]
by
-
or similar.
Still adding a random suffix to ensure uniqueness is a good idea probably!
This would result in
client_id
values which can be easily correlated with meshStack API Keys, even in external systems. Also configuration errors (using the wrong
client_id
) are easier to spot.
Also logging is improved, see https://feedback.meshcloud.io/feature-requests/p/display-api-user-and-api-key-information-in-logs