Feature/publish token authorization status from auth module

[wku12]

Before we go with that to EVerest, let's do internal review

[golovasteek]

Maybe add descriptions of the states here as well?

[wku12]

Aren't states self descriptive? What should I write there?

  TokenValidationStatus:
    description: >-
      Ongoing token validation status. 
      Idle mean that no token is currently processed.
      The first state after receiving the token is Processing.
      As soon as the token gets accepted, Accepted state is published.
      Whenever token gets rejected, Rejected is published.
    type: string

But this sounds weird

[dorezyuk]

Should we have different enums for accepted and used to stop and accepted and used to start a session?

[wku12]

What's the difference? Token is validated and accepted, right?

[dorezyuk]

Depending on what the use case is I think it does make a difference if the token is used to stop or start a session

[wku12]

I disagree. The following event will come later on. I think they added those return values just to make the code testable

[dorezyuk]

I don't understand - what is the following event ?

[wku12]

SessionEvent -> TransactionStarted/TransactionStopped

[wku12]

TransactionStarted: Signaled when a transaction has been started. Transaction starts at the point that all conditions for charging are met: EV is connected and user has been authorized
TransactionFinished: Signaled when the transaction finished. Transaction finishes at the point where one of the preconditions for charging irrevocably becomes false: When a user swipes to stop the transaction and the stop is authorized.

[dorezyuk]

My thinking was that we might want to differentiate if the token was used to stop (e.x show a yellow check mark) or to start (e.x Show a Green Check Mark)

Do you suggest to use the session event for this?

[wku12]

As discussed offline, we can always extend this message later
I'm creating a PR