Maximo Open Forum

 View Only

 Maximo development link unable to access for the users after SSL configuration

  • Everything Maximo
  • HSE/Oil and Gas
  • Infrastructure
  • Security
Mahadevan Ramakrishnan's profile image
Mahadevan Ramakrishnan posted 03-26-2024 04:12

Hello All,

We have been facing a strange issue recently on one of the Development environments after enabling SSL on all the lower environments. While the SSL enabled Maximo link is accessible across all environments, the Development environment after SSL enablement is accessible for us but unable to be accessed by any of the business users. We did check the browser version of the users and they are on the same version as us.

We are on Azure cloud and we checked with the Azure team and they replied that the Test VM and Dev VMs are indeed on the same vent and subnet. Additionally, they executed several PowerShell commands to test the network configurations. The results indicated that there are no DNS issues on either server.

Thank you,

Mahadevan

Jason VenHuizen's profile image
Jason VenHuizen

Assuming that it is not a network or routing issue, then it is likely a problem with the certificate. Recent versions of Chrome and Edge no longer report SSL errors such as expired certs or untrusted CA's but just don't show the site, which may look like the site cannot be accessed. Since the certificate is valid on your machine, but not on the end user's it may be an issue of the signing authority. If the cert was signed by an internal CA, as many government and large organizations have their own internal CA, you will need to add that CA to the end user's system trust store.  

Without more information it is hard to guess, but I would verify that your CA is valid on the user's machines.

Mahadevan Ramakrishnan's profile image
Mahadevan Ramakrishnan

Hi Jason,

Thank you for your response. Can you please clarify on the below points.

Also, we would like your assistance as to how we could enable the SSL on the websphere console as we are stuck up after doing all the configurations on one of the lower environment console as system is giving us the message,this site is not secure do you want to proceed.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Assuming that it is not a network or routing issue, then it is likely a problem with the certificate. [Mahadevan Comments start] - We also initially suspected that it could be related to problem with the certificate,but we used the same process by running the IKEYMAN utility of the rest of the environments- 3 VMs which are unclustered environment and Test environment which is a clustered environment and all those environments are working well with the certificate showing the CA signed one on the browser and users also able to successfully able to login. The issue is only with the development environment and nothing looks different between the Dev and Test environment.[Mahadevan Comments end]Recent versions of Chrome and Edge no longer report SSL errors such as expired certs or untrusted CA's but just don't show the site, which may look like the site cannot be accessed. Since the certificate is valid on your machine, but not on the end user's it may be an issue of the signing authority. If the cert was signed by an internal CA, as many government and large organizations have their own internal CA, you will need to add that CA to the end user's system trust store.  

Without more information it is hard to guess, but I would verify that your CA is valid on the user's machines.