Hi All,

I am generating JWT token and verifying it using Policy Nodes in Assembly(JWT-Generate & JWT-Validate).

Can we stop a call when we hit an API with the same JWT token more than one time with in the expiry time?

Consider a scenario where I kept TTL of JWT token is 30'secs. My Enduser is invoking the API 10 times in 30'secs with the same token. I need to restrict this, an end user should invoke the API one with one token  which is generated and if he is invoking the same API with same token another time within 30'secs an error message should be generated like "Token already used for one time. Generate token again and please comeback!!".

If yes, please guide me in this. And we try to achieve this by invoking the API with same token with in the TTL as many times as we can, until the token expires we didn't get succeeded.

So please anyone knowing about this issue can suggest me the best way to achieve this.

Doubt:

Runtime will generate the token this is for sure but when the time of verifying the generated token from where it is comparing both the generated and verifying token. So my question is where will the runtime store the generated token. If i want to access the token from stored location where will i get that.

Hi All,

I am generating JWT token and verifying it using Policy Nodes in Assembly(JWT-Generate & JWT-Validate).

Can we stop a call when we hit an API with the same JWT token more than one time with in the expiry time?

Consider a scenario where I kept TTL of JWT token is 30'secs. My Enduser is invoking the API 10 times in 30'secs with the same token. I need to restrict this, an end user should invoke the API one with one token  which is generated and if he is invoking the same API with same token another time within 30'secs an error message should be generated like "Token already used for one time. Generate token again and please comeback!!".

If yes, please guide me in this. And we try to achieve this by invoking the API with same token with in the TTL as many times as we can, until the token expires we didn't get succeeded.

So please anyone knowing about this issue can suggest me the best way to achieve this.

Doubt:

Runtime will generate the token this is for sure but when the time of verifying the generated token from where it is comparing both the generated and verifying token. So my question is where will the runtime store the generated token. If i want to access the token from stored location where will i get that.

Hi All,

I am generating JWT token and verifying it using Policy Nodes in Assembly(JWT-Generate & JWT-Validate).

Can we stop a call when we hit an API with the same JWT token more than one time with in the expiry time?

Consider a scenario where I kept TTL of JWT token is 30'secs. My Enduser is invoking the API 10 times in 30'secs with the same token. I need to restrict this, an end user should invoke the API one with one token  which is generated and if he is invoking the same API with same token another time within 30'secs an error message should be generated like "Token already used for one time. Generate token again and please comeback!!".

If yes, please guide me in this. And we try to achieve this by invoking the API with same token with in the TTL as many times as we can, until the token expires we didn't get succeeded.

So please anyone knowing about this issue can suggest me the best way to achieve this.

Doubt:

Runtime will generate the token this is for sure but when the time of verifying the generated token from where it is comparing both the generated and verifying token. So my question is where will the runtime store the generated token. If i want to access the token from stored location where will i get that.