alias

/remote/json-rpc

This property specifies the default alias where you can access the JSON-RPC provider. Please note, if you change that to something else, you can break a lot of web applications that have hard-coded the alias to the JSON-RPC provider.

service.secure.custom

false

The JSON-RPC provider allows developers to install new authentication providers by registering RemoteAuthenticator services. These providers will be used automatically, but you need to instruct the provider to use them. So in this property, you can specify a comma-separated list of RemoteAuthenticator service PIDs to be used when verifying access to remote services.

service.secure.https

If this property is set true, the JSON-RPC remote provider will always redirect the request over a secure (HTTPS) connection.

service.secure.ipfilter

Set this property if you want to limit the access and allow it only from the specified list of IP rules. The format of the property is '[rule]?[,rule]*'. Where rule is and IP address or IP range. Here is an example: 172.22.200.21, 192.168.1.0-192.168.1.32,10.8.0.1/16.

service.secure.rolefilter

Setting this property to something else than empty string will require a user login. If the user is not already logged in, he/she will be asked to do that via Basic HTTP authentication. Then it will be checked if the user has all the roles specified by this property. The roles are separated by comma.

service.secure.defaultcontext

true

Setting this property will force the JSON-RPC provider to call-back to the default HTTP context in addition to the security filters. This will automatically apply the default security scheme that is defined for the HTTP server.