[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBDS-1701) Update site for JBDS 4.0 is broken https://devstudio.jboss.com/updates/4.0
[
https://issues.jboss.org/browse/JBDS-1701?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1701 at 6/27/11 12:17 PM:
------------------------------------------------------------
Appears the solution here is to replace https:// with http://, in order to bypass any SSL
cert checking.
SO...
either we need to get approval from Legal to give out the http:// URL instead of the
https:// one (which, given there's no longer a password, is less needed but the goal
of https had been to guarantee bits transferred to customers were done so securely; also,
JBDS 4.0 users get the https:// URL preloaded in their installation so they would now have
to MANUALLY change that themselves, even if we change it for new users of JBDS 4.1 / 5.0)
or we file a ticket w/ whatever helpdesk / service center in Red Hat maintains the server
and get them to fix the SSL cert (?) on the server so that we stop getting these errors.
was (Author: nickboldt):
Appears the solution here is to replace https:// with http://, in order to bypass any
SSL cert checking.
SO...
either we need to get approval from Legal to give out the http:// URL instead of the
https:// one (which, given there's no longer a password, is less needed)
or we file a ticket w/ whatever helpdesk / service center in RH maintains the server and
get them to fix the SSL cert (?) on the server so that we stop getting these errors.
Update site for JBDS 4.0 is broken
https://devstudio.jboss.com/updates/4.0
--------------------------------------------------------------------------
Key: JBDS-1701
URL: https://issues.jboss.org/browse/JBDS-1701
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.0.0.GA
Reporter: Denis Golovin
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.1.0.CR2
Loading JBDS 4.0.0 Update site throws exceptions
{noformat}Some sites could not be found. See the error log for more detail.
Unable to read repository at https://devstudio.jboss.com/updates/4.0/extras/content.xml.
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid
certification path to requested target
Unable to read repository at https://devstudio.jboss.com/updates/4.0/content.xml.
sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid
certification path to requested target{noformat}
It has compositeContent.xml in it with
{noformat}
<?compositeMetadataRepository version='1.0.0'?>
<repository name="JBoss Developer Studio 4.x Updates"
type="org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository"
version="1.0.0">
<properties size="2">
<property name="p2.compressed" value="true"/>
<!-- date +%s000 -->
<property name="p2.timestamp" value="1303831787000"/>
</properties>
<children size="3">
<child location="4.0.0.GA"/>
<child location="jbds-target-platform/latest"/>
<child location="teiid/7.1.1"/>
</children>
</repository>
{noformat}
Using https://devstudio.jboss.com/updates/4.0/4.0.0.GA/ gives the same exception
jbds-target-platform/latest should not be included because update site built by product
build has all required artifacts in it.
Using https://devstudio.jboss.com/updates/4.0/teiid/7.1.1 gives the same exception
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira