Ask Flux
Help Center
How can we help?

Token Validator

Intended Purpose Token Validator:

Available under the Tools tab, the 'Validate Token' functionality allows us to obtain whether a token is valid or not, under the condition that the token is a roaming token. Token Validator searches for the Token inside the Token Cache in the GreenFlux platform.

An (external) eMSP's Token can be searched for/validated by entering one of the following values in the Token Validator wizard:

  • Auth ID
  • UID (ChipID)
  • Visual ID
Notion image

The Token Validator will search the Token Cache in the GreenFlux platform and will indicate whether the token exists in the Token Cache.  

When the Token exists in the GreenFlux Token Cache, the Token Validator wizard will show:

  • Visual ID
  • Auth ID
  • UID (ChipID)
  • Whether the token is Active or Inactive
    • Notion image
 

When the token doesn’t exist in the GreenFlux Token Cache (or when it is an OwnToken), the Token Validator wizard will show:

  • Unknown Token
Notion image

Token Validator Capabilities:

  • External Tokens: The User can use the Token Validator when the token is a roaming token and belongs to an external EMSP that has an active roaming agreement with GreenFlux CPO network.
  • Own Tokens: The User can use the Token validator when the GFX backend creates the token and roaming is activated.

Token Validator Limitations - The result will be unknown

  • External Tokens: The non-roaming and external tokens that even are roaming and concern eMSP that do not have an active roaming agreement with GreenFlux.
  • When Token Validator indicates that an external token is Unknown, it doesn’t mean that the token is invalid or that the token wouldn’t exist. Valid and active tokens of external eMSP’s that haven’t been pushed towards or pulled into our Token Cache are correct, but Token Validator can’t show it (yet) for such tokens.
  • Valid and active tokens of external eMSP’s that are roaming via Hubject – those are valid but will never be stored in our Token Cache because we do real-time authorisation with Hubject for all such tokens.
  • Own Tokens: If the token is non-roaming, the User should use the EMSP-Tokens screens in EV Portal, search for it, and verify the validity (e.g., whether it is active or not etc.)
Did this answer your question?
😞
😐
🤩