Method and Process for restricting usage of SPI implementations to approved implementations
Publication Date: 2015-Dec-23
The IP.com Prior Art Database
Use of 3rd Party implementations of SPI (Service Provider Interfaces) can be a risk to the infrastructure. The solution disclosed provides a mechanism to verify that an implementation of an interface meets all the requirements of the SPI. Once the implementation is proven a mechanism is provided to allow the implementation to identify itself as an approved implementation. This avoids the problem of rogue SPI implementations causing damage to the application or damaging the reputation of the company. This process is similar to the signing of drivers performed by some companies but takes place in an open environment.