New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Force token A usage when building authorization header when needed ? #19

Closed

lilgallon opened this issue Nov 2, 2023 · 1 comment

Labels

discussion module: transport

Member

lilgallon commented Nov 2, 2023

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 added discussion ocpi 2.2.1 module: transport labels

lilgallon mentioned this issue

fix(ocpi-2.2.1): Fixed usage of tokens & review PlatformRepository #16

Merged

lilgallon removed ocpi 2.1.1 gireve labels

Member Author

lilgallon commented Dec 8, 2023

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

lilgallon closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment