SHA1 Fingerprint Generated are different while using API and Logstash

[ikishorkumar]

Logstash information:

Please include the following information:

1. Logstash version logstash-8.11.3
2. Logstash installation zip
3. It's on the local
4. How was the Logstash Plugin installed by unzipping it

Description of the problem including expected versus actual behavior:
In our API, we are concatenating the order id and fingerprint to get the hashed value for orderKey.

Given the id/fingerprint of the items:
id: '7542b27c-c255-4b18-8321-06c9d65aca7f'
fingerprint: '28d68c4f04f487f514db3df32d36f70e31d27592'

The values concatenated together are '7542b27c-c255-4b18-8321-06c9d65aca7f28d68c4f04f487f514db3df32d36f70e31d27592', and our API is outputting '0c948678d0e2b308e178ea3a9e1e01c0f6ba79ef' for orderKey, but logstash output is 'bb5931eaed2186c3b4347401f0ae07e5fa98ed36'.

so i am just wondering why its different.

which library is being used for SHA1 one for the logstash.

we are using this in our app to generating the orderKey Hashed value and can be verified
https://emn178.github.io/online-tools/sha1.html?input_type=utf-8&input=7542b27c-c255-[…]d68c4f04f487f514db3df32d36f70e31d27592&hmac_input_type=utf-8