Hello Aaron, 

did you make the SSO integration?

If not then just follow the steps from the documentation: https://www.microfocus.com/documentation/arcsight/arcsight-platform-24.1/arcsight-admin-guide-24.1/#platform_integrate/ESM_data_user_overview.htm?TocPath=Integrating%2520the%2520Platform%2520Into%2520Your%2520Environment%257CIntegrating%2520ESM%25C2%25A0Data%2520and%2520Users%257C_____0

Best Regards, 

Daniel

Hello Daniel 

Thank you for your response. I have followed the steps outlined in the documentation, and it seems that the SSO configuration should be correct. I am able to view the relevant ESM rules on the user interface, and even access the CC UI independently.

However, when attempting to open it through the ArcSight platform, there is no response, and no messages, including error messages, are displayed. If you have any insights or suggestions on how to troubleshoot and resolve this issue, I would greatly appreciate your assistance.

Best regards,

Aaron

Hello Aaron, 

have you managed to connect via ArcSight Console ( configured to authenticate OSP Client Only Authentication ) and what is the result?

Best Regards, 

Daniel

Hello Daniel 

Thanks for your response.

I'm just tired of trying to find a solution for this. It seems like the Arcsight Platform ESM Command Center module just doesn't cut it in practical terms, you know? It's not really delivering the value it promises.

Best regards,

Aaron

Hello Arron, 

considering the complexity of the integration and the fact that there are so many parts involved i am recommending you recheck all the steps from the shared link: https://www.microfocus.com/documentation/arcsight/arcsight-platform-24.1/arcsight-admin-guide-24.1/#platform_integrate/ESM_data_user_overview.htm?TocPath=Integrating%2520the%2520Platform%2520Into%2520Your%2520Environment%257CIntegrating%2520ESM%25C2%25A0Data%2520and%2520Users%257C_____0

Do not forget this last step "Configuring the SSO Proxy" if you have a cluster deployed ( like min 3xmasters and 3x workes and other nodes for NFS and Vertica ...) and you are using VIP for access.

Did you manage to connect via ArcSight Console ( configured to authenticate OSP Client Only Authentication ) and what is the result?

Best Regards, 

Daniel

Hello Daniel 

Thanks for your response.

Do not forget this last step "Configuring the SSO Proxy" if you have a cluster deployed ( like min 3xmasters and 3x workes and other nodes for NFS and Vertica ...) and you are using VIP for access
=> Yes

Did you manage to connect via ArcSight Console ( configured to authenticate OSP Client Only Authentication ) and what is the result?
=> Yes,and It works

I can't Importing Certificates into the Fusion User Management TrustStore

I follow the steps from the documentation：Describing Authentication Details
https://www.microfocus.com/documentation/arcsight/arcsight-platform-24.1/arcsight-admin-guide-24.1/#platform_integrate/OSP_authentication.htm

The documentation has some errors

Aaron, 

you should follow the steps from this link "https://www.microfocus.com/documentation/arcsight/arcsight-platform-24.1/arcsight-admin-guide-24.1/#platform_integrate/ESM_OSP_configure.htm?TocPath=Integrating%2520the%2520Platform%2520Into%2520Your%2520Environment%257CIntegrating%2520ESM%25C2%25A0Data%2520and%2520Users%257C_____2" and be familiar with the concept if that's the case.

Are you planning to use "external authentication, such as SAML or LDAP" because i am confused as you mention this link: www.microfocus.com/.../

To conclude, in my lab where i use ESM with local authentication and wanted to switch on Fusion / SSO, I followed the steps from https://www.microfocus.com/documentation/arcsight/arcsight-platform-24.1/arcsight-admin-guide-24.1/#platform_integrate/ESM_OSP_configure.htm?TocPath=Integrating%2520the%2520Platform%2520Into%2520Your%2520Environment%257CIntegrating%2520ESM%25C2%25A0Data%2520and%2520Users%257C_____2 and works trust me.

If you do something else then try to mention it first.

Best Regards, 

Daniel

Hello Daniel 

"Thank you very much for your response and assistance. First off, I did follow your advice and went through the manual steps.

I've previously run ArcsightPlatform version 23.3, and everything worked just fine. However, with this version 24.1, I'm encountering OSP connection failure messages despite setting it up the same way. This is really puzzling to me.

The Arcsight Console also logs in via OSP and the connection is fine.

I hope this helps clarify the situation. Thanks again for your help."

Aaron

Hello Daniel 

"Thank you very much for your response and assistance. First off, I did follow your advice and went through the manual steps.

I've previously run ArcsightPlatform version 23.3, and everything worked just fine. However, with this version 24.1, I'm encountering OSP connection failure messages despite setting it up the same way. This is really puzzling to me.

The Arcsight Console also logs in via OSP and the connection is fine.

I hope this helps clarify the situation. Thanks again for your help."

Aaron

Hi aaron_hsia 

You will need to upgrade your ESM to 7.7. 

Platform and ESM now need to be kept lock-step with versions. 

E.g. if you have platform 24.1 you need ESM 24.1 (v7.7) 

However, in the absence of ESM being upgraded, you can still navigate to your ESM hostname to get into the original command centre 

Hi LewisJ,

Thank you for the update and clarification regarding the ESM upgrade. I appreciate the guidance on keeping the Platform and ESM versions aligned.

I will ensure that we upgrade our ESM to version 7.7 to maintain compatibility with the Platform. In the meantime, it's good to know that we can still access the original command center on our ESM hostname.

Thanks again for your assistance.

Best regards,
aaron_hsia

It also appears there's a bug in 24.1 where if your ESM usernames aren't in 'email' format, the fusion page won't redirect you properly and you'll get an error saying user not found. At least that is what is occurring in my environment. 

I've logged a support ticket for this. 

Hello Lewis, 

we are aware of this issue and we are working on fixing it.

In the meantime, the only solution in order to use the fusion integration is to accommodate the ESM usernames in 'email' format.

Best Regards, 

Daniel