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

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I am setting up Apache Devlake for the first time. I have poc'd it locally 
on my local laptop using Docker Desktop and connected to our 
Jira/Jenkins/Bitbucket applications and was able to configure data scopes (and 
pull data) without an issue.
   
   I have now been provided a VM and attempting to configure Apache Devlake 
again. Using the exact same credentials and to the same application endpoints I 
am presented with a 403 when attempting to 'Save' a data scope for Jira, 
Jenkins or Bitbucket. I am able to retrieve projects/repos using Apache Devlake.
   
   I can't see any errors in the container logs. Our network teams can see the 
requests traversing the network but there's nothing in the application logs of 
the failed requests on the Jira/Bitbucket/Jenkins side. Jira is cloud hosted 
(so external from our network), Bitbucket/Jenkins runs in the same on-premise 
network.
   
   I have attached a 403 from the network console. 
   
   Please let me know what other logs or configuration I can provide. 
   
   The logs have been somewhat anonymised.
   
   ### What do you expect to happen
   
   Saving a data scope should work.
   
   ### How to reproduce
   
   Adding a data scope for any saved data connection.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.1@e061ef2
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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