This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Wei Asatoopulakol
Nov 25, 2014, 12:23 AM
37 Posts

Why would Domino Access Services fail when using SSL?

  • Category: Application Development
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags: DAS,SSL,HTTPS
  • Replies: 6

I have an application which has a view exposed via DAS.

 

Everything works perfectly, and data is returned in the expected format whenever an HTTP call is made to the database. We use a URL similar to the following:

 

http://xxx.abc.com.au/web/data.nsf/api/data/collections/name/DocsByDate?start=0&count=10

 

We would like to secure communications to the web server and use SSL.

As soon as we use HTTPS to access the same database, however, we observe Error 403 (Forbidden).

Is there some additional configuration we have to complete to ensure DAS is available for both HTTP and HTTPS?

 

Any assistance would be most appreciated!

~Justin Chugerochekettu
Nov 25, 2014, 10:53 PM
19 Posts
Does the server return anything besides 403?
Additional info may help us figure out what is happening.  For example, does the response include a Content-Type header?  If there is a response body, please include that too.

Thanks.

-- Dave
~Wei Asatoopulakol
Nov 28, 2014, 2:02 AM
37 Posts
Here's some additional information...

Hi Dave,

 

Thanks very much for your reply. What can I tell you? The exact same URL is used in both cases... one (using HTTP) works perfectly and one (using HTTPS) does not.

The certificate is valid and I can review web content (web pages) using SSL without an issue.

The request/response data for the HTTP call looks like the following...

 

The request/response for the HTTPS call looks like the following...

There is nothing returned using HTTPS except the '403' error.

 

~Justin Chugerochekettu
Dec 1, 2014, 3:50 PM
19 Posts
I'm stumped ...
In the HTTPS case, the response includes a Content-Type header with a value of application/json.  This almost certainly means the request got as far the data service code.  The data service returns 403 for one of two reasons:
  • The data service isn't enabled on the server.
  • The data service doesn't have access to the specified database.

If an HTTP request works for the same server and database, I don't see how either of the above can be true.  Both requests are to the same server -- right?

-- Dave
~Justin Chugerochekettu
Dec 2, 2014, 12:32 AM
19 Posts
... but here's a tip from a colleague.
"make sure the customer does not have two internet site docs, one for ssl and one for normal http, in that case he would have to enable the data service for both sites.  In the ssl case we take the ip address the connection came in on and use that to look up the site (we do not use the host header/name), one can specify two sites one with a host name (http) and a separate one for ssl."
~Wei Asatoopulakol
Dec 4, 2014, 3:33 AM
37 Posts
Yep, I'm stumped as well

Thanks so much for persisting Dave!

 

A good tip from your colleague, but a thorough review of the DomDir revealed no issues with the existing Internet Site documents.

I am certainly accessing the exact same server/database with both commands - the only thing different is the protocol.

 

Funnily enough, web services that I have developed/exposed in the same database (simple Lotusscript agents that return JSON data) work fine when called via HTTPS.

So, this URL works fine...

https://xxx.abc.com.au/web/data.nsf/v1/doThisThing

... but this one does not...

https://xxx.abc.com.au/web/data.nsf/api/data/collections/name/DocsByDate?start=0&count=10

 

I've also just noticed something that may be a contributing factor here.

When I attempt to access the host root, I ALSO observe a 403 error. So going to https://xxx.abc.com.au, I observe...

 

Http Status Code: 403
Reason: Unable to process request, directory browsing is not allowed

 

This is getting even stranger!

It's not that I even want to access the root, but why on Earth would it reply with a 403 error?

The 'Internet Site' document lists the 'default home page' as 'index.html' (a flat HTML page) and going to https://xxx.abc.com.au/index.html works just fine.

 

I really need to sort this out and will continue my investigations/trials.

I'll let y'all know if I manage to get to the source of the issue.

 

Cheers!

~Chloe Brehipilitoden
Feb 16, 2015, 4:24 PM
1 Posts
SSL not working - we have the same problem

Hi Terry, I'm brand new to R901, so really have not much idea what I'm doing, but we want to do a similar thing to you, and are coming back with problems as well.

From a database design point of view, I'm checking the cgi field Server_Protocol, and it's reporting HTTP/1.1 every time.  It doesn't matter whether I'm using http or https in the URL.

All our online systems use a similar design method, and we build style sheets and relative links within each system dynamically, so referencing the correct protocol from cgi and using it to build internal links is being done on most pages.

I've looked through the web site document, the admin help, and several other places, and have come up stumped.

Did you ever get to the bottom of your isues?


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal