Open
Description
Issue reported that the Fleet service_tokens API can potentially result in conflict error.
The current logic uses the current timestamp in the token name, which is not unique.
The suggestion is to use the default behaviour of the ES API to omit the token name, in which case a unique token name will be generated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment