elapi whomai command does not work with API token without the ID prefix

[Cs137]

Many thanks for the nice CLI!

I just discovered that it the elapi whoami command does not work with "old" API tokens that do not contain the ID prefix. The change in the token's pattern is discussed in this elabFTW issue. If the "old" token is provided, the CLI aborts and raises the following error:

PatternNotFoundError("No API token ID prefix found in API token string!")

There is no need to address anything, I just created this issue to inform other users that might run into the same situation. Generating a new token is the obvious solution to tackle it.

[alexander-haller]

We should ether support old token format or at least show a proper error.

[mhxion]

If the "old" token is provided, the CLI aborts and raises the following error:

PatternNotFoundError("No API token ID prefix found in API token string!")

Hi. You get this error only when you run elapi whoami, right? Other commands should not bother and just send the API request as is regardless of the old/new API token. whoami command uses this ID to verify what permission your API keys have (r/w or read-only).

[Cs137]

Hi @mhxion,
Thanks for your response! I tried only the whoami sub-command, which caused the described behaviour and did not try other sub-commands (I should have mentioned it in the initial post - sorry). However, I reconfigured elAPI to use the "old" token and the other sub-commands are indeed working.

[mhxion]

@Cs137 Thanks for confirming. We can make it so that this read-write permission check is skipped and a warning is shown instead of an error (like Alexander mentioned) when an old-style API token is used.

[mhxion]

It should be fixed now. Please update elAPI to 2.4.10 and it should work again :)