Accessing Atrium programs using SSL

[chris_rover]

WE have configured atrium to run using SSL. However, when we select any programs in the Atrium menus, we get the following error:
"unable to reach server. Check your connection and try again."
Can anyone advise on what may be the problem?
It works on the non-secure instance.

[Scott Klement]

It probably means the server isn't running. Maybe it failed to start? Or, maybe you're trying to connect to a different address or port number than the one the server is running on?

It could also mean other things, like a routing error... but, it seems unlikely that this would be caused by an SSL configuration.

Also, FWIW, you didn't configure Atrium. Atrium does not have settings for SSL. You configured the IBM HTTP server instance that you have Atrium running on.

[chris_rover]

I stand corrected. We did indeed configure a secure web server to host Atrium. Atrium comes up fine when we invoke it in the url. the problem comes with when we select any of the programs running under it. We used the basic setup of the library and program names. These are all rich display programs by the way. is there anywhere else we might have overlooked, that the port number or address may be needed outside of the web server?

[Scott Klement]

Hi Chris,

I'm sorry that you are running into a problem with this.

My only guess is that somehow the directives in your httpd.conf file are not allowing this URL to work in your SSL setup. We have many customers using Atrium in SSL, and none have reported problems where Atrium itself runs, but Rich Displays do not. I just tried it, myself, a moment ago, and everything worked without problems for me.

Unfortunately, I do not know what is causing this problem. Atrium will launch Rich Display menu items by either opening them in an iframe (Atrium tab) or by opening them in a new browser tab. In either case, the URL it runs to launch the item will be similar to the following:

Code: Select all

https://your-system:port/profoundui/auth/start?atrium_item=XXX

Perhaps there is a mistake in your httpd.conf? If you're able to attach it to a forum message, here, I will look it over and see if I can spot any problems.

[chris_rover]

profoundSSL.PNG (150.71 KiB) Viewed 24457 times

As a follow up, we are stuck at this point when we try to access profound from using SSL. It seems to be somehow still pointing at the HTTP port of 8585 instead of the HTTPS. Can you advice please?

[Scott Klement]

This is a repeat of the message I posted on April 20, since that one appears to be showing as blank (not sure why):

Hi Chris,

I'm sorry that you are running into a problem with this.

My only guess is that somehow the directives in your httpd.conf file are not allowing this URL to work in your SSL setup. We have many customers using Atrium in SSL, and none have reported problems where Atrium itself runs, but Rich Displays do not. I just tried it, myself, a moment ago, and everything worked without problems for me.

Unfortunately, I do not know what is causing this problem. Atrium will launch Rich Display menu items by either opening them in an iframe (Atrium tab) or by opening them in a new browser tab. In either case, the URL it runs to launch the item will be similar to the following:

https://your-system:port/profoundui/auth/start?atrium_item=XXX

Perhaps there is a mistake in your httpd.conf? If you're able to attach it to a forum message, here, I will look it over and see if I ca

[Scott Klement]

Considering it looks like your application isn't working, I would strongly suggest contacting Profound Logic support rather than posting it as a public question for the community.

You can open a support ticket by e-mailing support@profoundlogic.com

[JohnAkers]

Quite an informative thread