Using EA to request a certificate from CA on behalf of AMT for TLS mode is successful, but the logging is confusing.

[mtpham-1]

Describe the bug 🪲

Running RPC local and leveraging EA to request a TLS certificate works, but when EA logs the transaction, it says "802.1x eap-tls request". This can be very confusing to customers.

To Reproduce 🪜 Steps to reproduce the behavior:

1. Go to 'EA' to setup the details for TLS mode configuration
2. From the vPro system, run command. This is example of Minh's command = rpc2.29.exe configure tls -mode Server -password P@ssw0rd -eaAddress "http://10.0.0.61:8000/" -eaUsername admin -eaPassword P@ssw0rd -v
3. Go to EA > Console and view logging
4. There is a line that say "802.1x eap-ls request". See screenshot attached.

Expected behavior Recommend changing this log to say something generic like "Certificate Request."

Screenshots 🖼️

AMT Device (please complete the following information): 🖥️

• OS: [e.g. Linux Kernel & Version]
• AMT Version: [e.g. 11.8.5, 12.0.45]
• AMT Configuration Mode: [e.g. Admin Control Mode or Client Control Mode]
• Network Configuration [e.g. Dynamic IP or Static IP]

Service Deployment (please complete the following information): ⛈️

• Deployment Type: RPC local provisioning
• Component & Version: EA version 2.29

[mtpham-1]

I forgot to mention, this configuration is for enterprise TLS mode, not 802.1x config, that is why it will be confusing to the customer. Change it to read a generic term like "Certificate Request."