Here you can add, modify or delete permissions on the communication services this connection will allow the client to execute.

When you create a new Connection, this option will be empty, and you need to manually specify what permissions you want to allow.

If you don't specify any permission, than this connection will be useless.

The All permission will allow any service to be executed by this connection.

In previous versions of MIS Communicator, you could not setup these permissions, so it would be equivalent to having All.

In a development environment you may wish to have the All permission active so you can test and use any communication function, but when you deploy MIS Communicator into a production environment, you should only enable permissions that are actually required by your client applications to limit the surface area of attack to an eventual intrusion attempt.

In several options, like Receive Files you can filter the allowed folders that the permission is allowed access to. If you need multiple folders, you can add multiple entries to this list for the same permission.

The permissions in the list, are self explanatory and most of them have the name of the corresponding Kalipso action.

Setting this permissions correctly is very important, specially if you are exposing MIS Communicator connections to an external network.

Last updated