What sites + what ports needs to be reachable for the signing tool C:\Program Files (x86)\Skyline Communications\Skyline DataMiner Protocol Builder\SLDMProtocolBuilder.exe
Our security department is very severe. Now they have implemented segregated networks. The build server is cut off of the outside world. But for the Skyline signing tool this build server needs to have access. They want only give access to the bare minimum.
They gave the build server access to
www.skyline.be
protocol.skyline.be/api/Soap.asmx
But this is apparently not enough.
Please give me a list of sites and ports the signing tool needs, because it has to pass a waterfall of authorities to allow access (American style apparently) and in the mean time no new DMAPP can be build => customers cannot get their fixes,...
Notice
Please note that this tool is no longer being maintained and was primarily intended for internal use.
.NET Tooling for .dmapp and .dmprotocol Packages
For the creation of .dmapp or .dmprotocol packages, we have provided access to platform-independent .NET tooling that can be utilized by the broader DevOps community. Package signing is exclusively performed within Skyline, using Skyline's internal pipelines. Currently, there is no feature available for signing packages using other company-specific certifications.
Packager .NET Tool
The Packager .NET tool is designed to create application packages. For detailed information on supported package types and instructions on installation and usage, refer to the Skyline.DataMiner.CICD.Tools.Packager. This tool is typically used in scenarios such as creating an application package from an Automation script solution folder (e.g., as a step in a CI/CD pipeline). It supports creating application packages for:
- Automation script solutions
- Visio repositories (both protocol Visio files and others)
- Dashboard repositories
Additionally, the Packager tool can create protocol packages (.dmprotocol) for protocol solutions.
The source code is publicly available, allowing you and your security teams to review it to ensure it meets your security requirements:
Skyline.DataMiner.CICD.Packages on GitHub
You can also find examples of how to manually use these tools from a command line environment:
Hi Cristel,
SLDMProtocolBuilder will only contact the soap service on https://protocol.skyline.be/.
Can you confirm your build server can reach https://protocol.skyline.be/api/Soap.asmx by testing it in a browser?