It is not provisioned when using TLS-PKI.

[jic5760]

An Endpoint Group was created using TLS-PKI and EMAAgent was executed.
But the Intel ME is not provisioned, so the CIRA is not connected.

I can't find any logs even in the "Intel Management and Security Status" program in the Client.
Is there any way I can see the log to find out why?

[Victor_G_Intel]

Hello jic5760,

Thank you so much for your response.

As of now in order to continue investigating this issue further we will be sending you a private email requesting some information, please be aware of your email and respond only to the email and not the thread for now.

Best regards,

Victor G.

Intel Technical Support Technician

[Victor_G_Intel]

Hello jic5760,

Thank you so much for your response

Based on the information that you provided internally, we have found that the issue you are experiencing is due to an issue with a mismatch between the EMA agent file and the EMA server’s FQDN. We will be providing more information via internal email and as soon as we have a resolution, we will share it here on the thread.

Note: Please only respond to the email that we will send later today. Also, we checked the other thread that you shared, but please bear in mind that is not necessary to handle this situation in two threads at the same time, we can work on everything on this thread as long as it is related to the same environment; therefore, the other thread will be closed to avoid any confusion on both ends.

Best regards,

Victor G.

Intel Technical Support Technician

[Victor_G_Intel · Accepted solution]

Hello jic5760,

Thank you so much for your response.

We are glad to hear that the problem with CIRA has been fixed.

Please find your questions answered below:

1-Is the FQDN not changing in the Web Management UI a bug in EMA? Or is it not originally intended?

R/It is not a bug, as per our knowledge, it is intended that once you complete the configuration the only way to change the FQDN is to re-do the configuration from scratch, there isn’t really an instance where you need to change it unless there is a problem related to it.

2-In a multi-tenant environment, the FQDN of the server and the FQDN of certificates are inevitably different. How do these cases work?

R/You can create as many groups and as many tenants, as you like with the certificate you created, there is no need to create new certificates for every tenant although you can; however, it won’t be recommended.

Best regards,

Victor G.

Intel Technical Support Technician  

[Victor_G_Intel]

Hello jic5760,

Thank you so much for your response.

We are glad to know that you found the information provided helpful. We will proceed to close the thread; however, feel free to contact us back at any time by submitting a new question or by contacting us through any of our other support channels.

Best regards,

Victor G.

Intel Technical Support Technician