Exposing JAZZ to the outside world
![]() Has anyone exposed their JAZZ instance to the outside world? I'd like to hear on your implementation/troubles. We are in the process of exposing our JAZZ instance to our customers (external companies). Internally we support users from two different networks, both stand-alone Windows AD forests. We however are currently using tomcat for user management. One of the security concerns from our security group is password aging/security features. Another concern is our network groups ptoposed implementation. We are currently running https internally. Management has suggested to drop https internally and encrypt the traffic going externally (https ?). My concern here is the URI and whether this would work. I don't claim to be a network/web guru but if external users are using https://jazz..... and our URI is http://jazz ... would this be a problem?
Norm
|
2 answers
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.