I don't see any change in the monitoring data and I still see SNCFRAME in the packets when inspecting them via Wireshark (captured on AMD with keytab files present and config done as per docs).
If more detailed help is needed, please, report support ticket and you'll receive assistance from our support and development teams.
If you're using HS AMD (12.4.15 or later), you can use the 'rcon' command:
to help figure out if your keytab files are being used/recognized. That command is not available in Classic AMD though.
Indeed, not what you want to see! 😉
This is more what you want:
Dynatrace RTM Console, ver. ndw.22.214.171.124 RHEL7_x86_64
Log file: /var/log/adlex/rcon.log
>$ sncdecr status
SNC DECRYPTION STATUS:
NO KEYS AVAILABLE tells me that the keys are either not present, or not loaded in memory. Did you follow the steps in the docs, how to create the keylist file etc.? That's assuming the keytab files you have, are correct and of a supported SNC library, of course. Something like SAP's GSS-API v2 over NTLM (SSPI) is not a supported library, since NTLM is not supported, only Kerberos.
We have a SAP SCM implementation that is monitored with SAP GUI and SAP GUI over HTTP decodes. Also for those we like to know if decryption is working.
I am not familiar to SAP. Perhaps the keys are not needed there?
I'm learning as I go along, I'm no SAP expert myself, not by a long shot!
What I can say is that from what I've seen, if you have SNC traffic on the wire, and you're using a 2017 or newer AMD, you will see SAP-SNC-Encrypted traffic if you look at the SAP GUI software service's Operations.
If you don't see that, chances are good SNC is not used; the SAP BASIS team should also be able to confirm if SNC is implemented or not.
If you do see SNC traffic in NAM (DCRUM), you'll need the keytab files to decrypt the SNC traffic on the AMD. But they have to use Kerberos, as NTLM is not supported.