Skip to content
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.

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

Token invalid #1

Open
witchi opened this issue Sep 10, 2024 · 0 comments
Open

Token invalid #1

witchi opened this issue Sep 10, 2024 · 0 comments

Comments

@witchi
Copy link

witchi commented Sep 10, 2024

Hi,

You have added an allowedUses attribute to the server tokens, so it seems there will be a problem with the client access using tokens.

I generate a token-id (ReadPatientsToken) with Session.getTempId() against a v1.12 Mainzellist server. This Id will be cached within the Session class, but we can it use only once. The default allowedUses within the server is 1 for every token (also for ReadPatientsToken), and the client class will not set another value within the JSON data.

So I think, that it will be necessary to set allowedUses to Integer.MAX_VALUE or provide a method to set it from outside Session by customer code.

I use an old library with API-Version 2.0, maybe there are differences on the server. Your current API seems to be 3.2.

Thanks
André

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant