Generate signature
An openOBD function can be called from another openOBD function. Before the function can be published on the Jifeline infrastructure it needs to be assigned a unique identifier. Along with this identifier, a signature is needed, that is used as proof that you are the actual owner of the function.
Below we show example code that can be used to obtain a unique function id and signature.
Info
We do not need to execute this, we can use our fresh_signatures.py script (defined here) to retrieve signatures for our functions.
Here, we demonstrate that signature creation is a one-time operation at the creation of your script.
When you want to test this, copy this to a python file (.py) and make it executable by this command line:
chmod 755 <filename.py>
Then, run your script, and see that it simply generates a fresh id and signature.
Register your EOBD script
- Run the script to generate fresh signatures for your functions (defined here).
./fresh_signatures.py
- Notice: every time you run this script, new id's and signatures will be generated.
- Copy the
idandsignaturefor your EOBD script and make them permanent by copying them into the EOBD script. - Run your overview script:
./overview.py
and check that the id and signature of your EOBD script are now fixed every time you run this script.
Registering your scripts with a fixed id and signature is important in case you want to make function calls from your function
to other functions.
But first, we will try to get our function on-line on our partner dashboard.