The idea here is that third-party service could have the right to change the OCNrules of a party. This allows that the white-&blacklist of a party is managed by a contracting service for example. As soon as a commercial agreement is made on this contracting service platform, the white-/backlist is changed accordinlgy and eRoaming via the OCN is enabled.
Two permissions must be added to the permissions list smart contract:
17 ocnrules_read Third-parties can read the OCNRules White/Blacklist of an OCPI Party
18 ocnrules_cud Third-parties can write the OCNRules White/Blacklist of an OCPI Party
Original report by Christopher Burgahn (Bitbucket: [Christopher Burgahn](https://bitbucket.org/Christopher Burgahn), ).
The idea here is that third-party service could have the right to change the OCNrules of a party. This allows that the white-&blacklist of a party is managed by a contracting service for example. As soon as a commercial agreement is made on this contracting service platform, the white-/backlist is changed accordinlgy and eRoaming via the OCN is enabled.
Two permissions must be added to the permissions list smart contract:
The OCN Node must then allow this behaviour.