#578 Rest API does not work on d9 -> d10 upgrade instances
Closed: Fixed None Opened 11 years ago by rcritten.

To reproduce:

The update to IPA 3.1.3 may not be necessary. We found this using ipa cert-find which is only in 3.1.3.

The error returned is:

RuntimeException: org.apache.http.conn.HttpHostConnectException: Connection to http://localhost:8080 refused


Decision is not to support restful interface in upgraded d9 instances. This effort would require lots of porting as d9 instances are tomcat6 based, and the rest authenticator ad realm are all tomcat7 based.

Instead a servlet will be added to return 501 (Not Implemented) when the rest interface is accessed on d9 instances.

Here is the commit message:

commit 7513de3348363df72e4be1305215fb181b78a8d5
Author: Ade Lee alee@redhat.com
Date: Fri Apr 19 11:27:28 2013 -0400

Added servlet to return 501 for rest operations for d9 instances

D9 instances run on tomcat6, which does not have support for the
autheticator and realm.  We are not supporting the REST operations
on D9 style instances.  They will need to be migrated.

The migration framework has been modified to process d9 or d10
style instances, and a migration script has been added to add the new
servlet to existing d9 instances.

An additional small patch is required to ensure that we deliver the /var/log/pki
directory. That is coming shortly.

Metadata Update from @rcritten:
- Issue assigned to jmagne
- Issue set to the milestone: 10.0.2

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1148

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata