OAuth Certificate Authentication
We have extended our OAuth2 support to include Client Certificate Support in place of a Client Secret.
Certificates are loaded from the Windows Certificate Store and therefore the process will need access to the Private Key. If you use the LocalMachine certificate store then ensure that the Ouvvi Service user has permission to read the private key. Additionally if you want to manage the connection from Ouvvi ensure that the Ouvvi AppPool user also has permission to the private key.
In this version 6.0.3372 we have support for using certificates with authorization_code and client_credentials flows with the following connectors.
- SharePoint Online
- SharePoint FileStore (used to access data inside Excel/CSV files in a document library)
- Dynamics 365
- SQL Azure
- JSON API Tool
You can specify either the thumbprint or subject name as the certificate setting in the connection.
You can also specify the full path i.e. LocalMachine\My\DataSync-SharePoint or just DataSync-SharePoint and we will look for the certificate in the My store location in both the LocalMachine and CurrentUser stores.
Since we now support certificates its possible to connect with SharePoint using client_credentials flow and use application level permission rather than a delegated user. This prevents your integration projects being tied to a user account.
Ouvvi Time Trigger - Window
We had a customer request to prevent Time Triggers to running after a certain time. By default if a trigger time is missed due to the service not running because if an IT issue or similar, The trigger runs when the service is restarted. Generally this is what you want, However for this customer they did not want to run resource heavy overnight tasks during the day if this occurred.
The solution to this is a new EndTime setting on the Time Trigger which defaults to '23:59:59'. Now if the End Time period has passed the trigger does not evaluate and therefore start the attached projects. So you can now configure a Time Trigger to run between say 03:00:00 and 05:00:00 to prevent the trigger running after 5AM.
Ouvvi Desktop - Client
We have been experimenting with an alternative Desktop Client for Ouvvi. This client connects directly to the Ouvvi Database and therefore bypasses the IIS Web components of Ouvvi. This also allows us to make some changes to the Ouvvi Windows Service to connect directly to the database and bypass the need for the Web Server altogether.
There are both advantages and disadvantages to this approach. On one hand it simplifies the deployment, connecting to a SQL Database can be done from almost anywhere and you can manage the security at the database level. On the other we loose some features of being a Web Application and anyone interacting with Ouvvi would require the Client installed.
We would like some feedback from our customers whether this seems a good idea before we spend too much time on it?
Ouvvi Desktop Client - Screenshot
