1 2 Previous Next 28 Replies Latest reply on May 25, 2018 6:23 AM by Edison Pioneer

API stopped working after applying SSL to REST API

Edison Pioneer May 9, 2018 4:28 PM

Share This:

Hi fellas,

Currently Remedy REST APIs in my clients organization are HTTP based. However, it should be with HTTPS connection. As per the guidelines in

https://docs.bmc.com/docs/display/public/ars9000/Configuring+the+REST+API#ConfiguringtheRESTAPI-ToconfigureRESTAPIforHTTPSconnection

we made necessary changes.

After the changes, it is not working at all. We have tried with following options -

1. Imported client system's Certificate and followed the process to configure from HTTP to HTTPS. (Post changes in jetty-selector.xml and restart of Remedy service, API stopped functioning)

2. Created new certificate as per the steps provided in the BMC doc from above link. Created the Keystore. Modified the jetty-selector.xml. (Post Changes in file and restart of Remedy service, API stopped functioning)

********************************************************************************************************

We performed the steps which are given in the link .However, API‘s are not responding at all. Getting following error when tried to consume it through postman.

After applying the settings, API ’s with HTTP settings are also not running.

We checked for the below 2, but they are fine

********************************************************************************************************

Also we gathered arerror.logs

I have not attached the entire logs, but the only those part of the logs where I think point towards whats going wrong (Attachment name - Logs snippets JMS exceptions)

If required, I will attach the entire logs I got, but I don't think there's anything significant to be found.

Kindly advise on what can be done here.

Thanks in advance

Log snippets JMS exceptions.txt 14.6 K

1. Re: API stopped working after applying SSL to REST API

LJ LongWing May 8, 2018 3:23 PM (in response to Edison Pioneer)

You'll need to provide more information than 'it stopped working'....what are the errors, are there any logs?
Like Show 0 Likes(0)

Actions
2. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 9, 2018 12:42 AM (in response to LJ LongWing)

Hi LJ,

What logs should I be taking?
API+Fltr+SQL?

Should I be looking into arerror.log as well?

Need I replicate the issue? As in, revert back to pre-SSL and again apply SSL while collecting logs?

Please let me know in case I am missing out on something.

Thanks.
Like Show 0 Likes(0)

Actions
3. Re: API stopped working after applying SSL to REST API

Carl Wilson May 9, 2018 7:06 AM (in response to Edison Pioneer)
Hi,
I think LJ also means things such as:

Is this a Self Signed Certificate or a chained Authority based Certificate?
What is the configuration changes you made to Jetty, and did you validate the certificates?
What do the Jetty logs show for the actual issue?

There is differences that are not listed in the BMC instructions for Authority based Certificates, they only list how to create a Self Signed Certificate keystore and point the Jetty configuration to this - so know the exact steps you did to create the keystore and update the configuration, etc would help.

Cheers
Carl
Like Show 1 Likes(1)

Actions
4. Re: API stopped working after applying SSL to REST API

LJ LongWing May 9, 2018 8:54 AM (in response to Carl Wilson)

Yes...but also 'when I try to hit the url I get 'this'.....what do you get....what's in your jetty logs...'doesn't work' doesn't tell us ANYTHING other than it's not working...we need to know what errors you are getting in what log files to be able to try and help you out.
Like Show 1 Likes(1)

Actions
5. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 9, 2018 4:29 PM (in response to LJ LongWing)

Hi LJ,

I have updated the main discussion part, and also attached snippets from arerror logs.
Will try gathering the jetty logs tomorrow.

Thanks for your interest. Let me know if you find anything or anything more is required.
Like Show 0 Likes(0)

Actions
6. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 9, 2018 4:31 PM (in response to Carl Wilson)

Hi Carl,

I can find out only tomorrow if the certificate was self signed or issued by a CA.
For now, I have updated the main discussion part and attached snippets from arerror log.

Would you please check and revert your feedback?

Thanks for taking interest
Like Show 0 Likes(0)

Actions
7. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 10, 2018 7:13 AM (in response to LJ LongWing)

Hi LJ,

I am about to gather jetty logs following the instructions in DOC 50147 below. This requires making changes to jetty.xml and then restarting the server.
https://communities.bmc.com/docs/DOC-50147

However, DOC 96343 has also come to my attention. It details on how to gather REST API logs. We need to make changes to logback_server.xml
https://communities.bmc.com/docs/DOC-96343

Just wanted to have your feedback if I should follow DOC 96343 as well to gather REST API logs?

Thanks.
Like Show 0 Likes(0)

Actions
8. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 10, 2018 7:13 AM (in response to Carl Wilson)

Hi Carl,

I am about to gather jetty logs following the instructions in DOC 50147 below. This requires making changes to jetty.xml and then restarting the server.
https://communities.bmc.com/docs/DOC-50147

However, DOC 96343 has also come to my attention. It details on how to gather REST API logs. We need to make changes to logback_server.xml
https://communities.bmc.com/docs/DOC-96343

Just wanted to have your feedback if I should follow DOC 96343 as well to gather REST API logs?

Thanks.
Like Show 0 Likes(0)

Actions
9. Re: API stopped working after applying SSL to REST API

LJ LongWing May 10, 2018 8:14 AM (in response to Edison Pioneer)

Correct me if I'm wrong please, but when you go from HTTP to HTTPS, you typically don't stay on the same port. Looking at the default configs 8008 is the default HTTP port, and the default HTTPS port is 8443....did you define the https port as 8008, or is it defined as 8443 and you are hitting a now non-configured port?
Like Show 1 Likes(1)

Actions
10. Re: API stopped working after applying SSL to REST API

Danny Kellett May 10, 2018 11:30 AM (in response to Edison Pioneer)

Not sure if this is a type but the third and forth URLs have period / full stops and not colons.
Kind regards
Danny
Like Show 1 Likes(1)

Actions
11. Re: API stopped working after applying SSL to REST API

LJ LongWing May 10, 2018 11:58 AM (in response to Danny Kellett)

good catch....didn't see that myself but you are correct....those are periods and not colons....
Like Show 1 Likes(1)

Actions
12. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 10, 2018 12:11 PM (in response to LJ LongWing)

Hi LJ,

Thanks for pointing this out!

Do we need to mention the HTTPS confidential port - 8443 only in the web link , or make any changes to other files as well?
I am planning to check the jetty.xml and jetty-selector.xml file tomorrow since the configuration was made by another person, and hes not available now.

Thanks.
Like Show 0 Likes(0)

Actions
13. Re: API stopped working after applying SSL to REST API

Edison Pioneer May 10, 2018 12:12 PM (in response to Danny Kellett)

Thanks Danny
Like Show 1 Likes(1)

Actions
14. Re: API stopped working after applying SSL to REST API

Carl Wilson May 10, 2018 12:18 PM (in response to Edison Pioneer)

Hi,
The port that you specify for HTTPS is set in the jetty configuration, so
it can be any port not in use and does not have to be a "standard" HTTPS
port.

Cheers
Carl
Like Show 1 Likes(1)

Actions