Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application invocation URIs don't support SSL secured links #826

danielmarbach opened this issue Apr 9, 2019 · 0 comments


None yet
2 participants
Copy link

commented Apr 9, 2019

Who's affected

Customers using application invocation links with si://


Because we use isolated storage for storing profiles it is difficult to use register multiple ServiceControl URIs in the profile settings. As a workaround, we suggest using

In theory links like si://anyknownserver:3333/api for example should open ServiceInsight and connect to http://anyknownserver:3333/api

Unfortunately, there is an issue with the approach:

If the actual ServiceControl instance uses SSL the replacement of the link is [](hardcoded to use http://) without SSL redirects those links will not work


Force redirects from http:// to https:// (needs to be verified)

@HEskandari HEskandari added the Bug label Apr 9, 2019

HEskandari added a commit that referenced this issue May 23, 2019

@HEskandari HEskandari added this to the 1.13.0 milestone May 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.