Configuration File Conventions
Service Locations
Service locations in the configuration file are specified similar to normal URLs. For more information on URLs, see the URL spec. There are several protocols that MV3D supports. The main two are Perspective Broker and HTTP. These use the pb and http (or https) protocol names respectively. For more information on protocols available with MV3D, see ProtocolServices. In addition to the protocol, host, and port of the URL, it is required to add in the service name. This takes the place of the path in the URL. Here are some example service locations as they would be used in a configuration file:
https://login.mv3d.com:8080/Login pb://localhost:1999/Dir pb://admin:pass@someserver.com:1999/Player
Login information can be included in the URLs in the normal way. However, when specifying which authentication method to use (if not using the default), it is specified after the user name separated by a comma:
pb://admin,local:pass@localhost:1999/Asset
For more information on authentication methods, see ArchitectureAuthentication. Multiple service locations should be separated by a comma. Currently this is not compatible with selecting a non default authentication method. Example of multiple services for a single configuration option:
pb://localhost:1999/Asset, pb://someserver.com:1999/Asset
Permission Specification
Most services can be configured to accept a list of users and groups that are allowed to access functionality of the service. For more information on permissions and security, see ArchitecturePermissions. There are two ways of specifying permissions: grantPermissions and denyPermissions. Both of these are specified in the same format: permission:<user or group>. Multiple permissions should be seperated by commas. Some examples:
grantPermissions=reference:all, read:all, modify:admin, edit:george denyPermissions=all:evilHackers
The keyword all can be used for either side to denote that any user or any permission will pass the rule. It is also valid (but usually not wise) to specify all:all to allow or deny all permissions and all users.
