Idea ID 2867310
We would like to use External Actions for example to create custom Reports. The User can select all the Workitems he wants to Export in an Excel and then Click the External Action Button. The Problem here is that the Endpoint of the listening server would be open for everyone. That could be limited by making this enpoints only available in the companys network but would decrease usability (because you have to connect to VPN and external Stuff is not getting access) and also is not the way we would like to build that.
What would be needed is some way to either do an authentification on the enpoint listening server. For example with the "Credentials" Configuration that already exist for Webhooks or what even would be better is an "internal external action" 🙂 Meaning that I can put in an option so the Octane Server instead of the User makes the connection to the listening server and everything stays within the "Application" Network zone. That way the listening server is not exposed. It would be really great if both of these points will be possible in the future so we can hold up a high security standart and protect the data that is in octane.
With ALM you didnt had that problem because you could simply use VBS inside Octane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.