Force token A usage when building authorization header when needed ?

[lilgallon]

I wonder if we want to "allow" the use of tokenA, or actually force to use it? The only case of using tokenA is when we initialize the credentials handshake, where we call 3 endpoints with tokenA (and in that case we are sure we want to use tokenA). Then we will always use the client token. I will go on with the review to see if what I say makes sense or not.

Originally posted by @xhanin in #16 (comment)

[lilgallon]

We want to be able to "allow" it, it was cleared up with a long time OCPI partner