ajoecker1 opened a new issue, #8709:
URL: https://github.com/apache/incubator-devlake/issues/8709

   <!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
   -->
   
   ## Question
   I try to set up a JIRA Cloud connection for our cloud instance. So I use 
_https://xxx.atlassian.net/rest/_ as the endpoint and give the credentials.
   
   When I test the connection, it fails with the following message
   `
   Get "https://sartorius.atlassian.net/rest/api/2/serverInfo": tls: failed to 
verify certificate: x509: certificate signed by unknown authority`
   
   For all our other JIRA api connections (outside of DevLake), the URL we are 
using is _https://sartorius.atlassian.net/rest/api/3/_ so we are using another 
version than devlake and I assume the error comes from using _2_ instead of _3_.
   
   Can I configure this somehow ? Because giving the full URL 
__https://xxx.atlassian.net/rest/api/3/_ is also not working, as it simply adds 
the _/api/2_ at the end.
   
   ## Screenshots
   If applicable, add screenshots to help explain.
   
   ## Additional context
   Add any other context here.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to