Is my FMC integrated with SecureX?

[atsukane]

Apologies for the duff title and question in advance.

I've registered using our CCO account and linked organisation and integrated FMC with SecureX and I can see events on SSE.

However, "Enable SecureX" button is still in the SecureX Integration menu on FMC and I don't have the SecureX ribbons anywhere.

So I'm guessing something has gone wrong somewhere and not sure where to look or how to start from scratch.

Is it just a matter of unlinking smart account and lining it again?

FMC version is 7.2 and FTD is 6.6.5

Many thanks,

[ben.greenbaum]

If you are seeing events in SSE your FMC is connected to SecureX.

What you still need to do is connect SecureX to your FMC.... 
What happens when you click the "Enable SecureX" button?

[atsukane]

Thanks @ben.greenbaum 

I get redirected to SecureX page and also there's a pop up on FMC "Please verify the code provided by SecureX." with a code. But I don't see anything in the SecureX site.

[atsukane · Accepted solution]

So it turned out the FMC was redirecting me to a wrong URL.

Engaged with TAC SecureX team initially. From SecureX side everything looked fine, then we looked at integration from FMC and he noticed that "Enable SecureX" button under the Integration menu on FMC was redirecting to a wrong URL.

We are based in Europe and despite selecting the EU region, it was redirecting us to US region. https://visibility.amp.cisco.com/

We then engaged with an engineer in FMC team and he confirmed that SecureXFQDN value in the config was wrong. 

Before:

He checked internally and confirmed that changing this value do not present any issues so proceeded to change the SecureXFQDN in the securex.properties to the correct value of "https://visibility.eu.amp.cisco.com/" and restarted the SecureX services (SSEConnector) on FMC.

After:

It didn't work straight away and we had to reboot the FMC VM but after a reboot the Enable SecureX button redirected my request to the correct URL and I was able to complete the integration finally.

[ben.greenbaum]

Thank you very much for the followup, and I'm glad to read that it got resolved!