OMF connections best practices

Successful OMF connections depend on using the correct client credentials and configuring security correctly. We recommend the following best practices for OMF connections:

• Each type of application or system that sends OMF data to CONNECT data services should have its own defined OMF connection, with the name and description referencing the data source.

• Each application instance or each device that sends OMF data to CONNECT data services should have its own client credentials client and its own secret. Connections allow a list of clients to be defined. When each application instance or device has its own client, security is improved because secrets can be managed at a granular level.

• The client credentials client should have the minimum roles and access. For example, a client may be granted access to write data, but it does not have permissions to delete data. Note, however, the permissions associated with the OMF connection are separate from the client's permissions, and restrictions on the client do not impact permissions on OMF messages.

• For use cases that involve a large number of source applications or source devices, the API can be used to automatically assign a new client credentials client and secret whenever a new device is brought online.