More than one active key found in crypto module warning when running an ATF test

[Dave65]

Good Day and thank you in advance for your help.

I am running an ATF test and when it succeeds. it succeeds with warnings. The warning is what I have shown below.

"More than one active key found in crypto module wit sys_id: fb0da86f53203010e5f7ddeeff7b12d6 for key type id: sym_hmac: no thrown error"

Other times the test fails. Either way, it is always on the same step, Submit a Record producer.
I can submit a record manually using the record producer and never run into this problem.
I can't find any documentation on this error. has anyone else run into this?

Thank you for your help!

[Shaqeel]

@Dave65 

After Run,

click "Add all warning to ignore list" and run again, you won't get any warning this time.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting "Accept as Solution" and " Helpful." This action benefits both the community and me.

*************************************************************************************************************

Regards

Shaqeel

[Dave65]

We are trying to figure out what the warning is telling us. We don't just want to ignore the warning.

[Shaqeel]

Hi @Dave65 

Okay Then, this is what I found:

The message suggests that an operation involving an HMAC key type (sym_hmac) is occurring, but no error is being thrown explicitly, which can make debugging a little tricky. Here are some potential reasons and steps you can follow to investigate and resolve this:

Potential Causes

1. HMAC Key Misconfiguration:
• There may be a misconfiguration with the HMAC key (e.g., incorrect key format, missing key, or unsupported algorithm).
2. Encryption/Decryption Issues:
• If you're using encryption or hashing functionality that relies on an HMAC key (e.g., in REST API calls, OAuth, or authentication processes), the issue could stem from the encryption configuration.
3. Missing or Incorrect Key in Credential Store:
• In some cases, the key might be missing or incorrectly set in the credential store (e.g., OAuth tokens or API keys).
4. Integration Problems:
• If the system is interacting with an external system (like an API or external service) and using HMAC for signing requests, there might be a problem with how the request is being signed or validated by the external system.

You can check the script where HMAC is being used.

Regards

Shaqeel

[You-Lan Bribach]

Hey Shaqeel,

I encountered the same warning message and how do you "After Run, click "Add all warning to ignore list"? I did not see the UI action.