Add optional field to mark token as suspicious
See original GitHub issueThe end goal is to have an optional boolean
field called suspicious
which will mark the token as suspicious. This will be tracked with the git commit but will be used in (hopefully) good faith to mark tokens that are not the official ones as suspicious - such as fake governance tokens.
See https://twitter.com/sniko_/status/1279874748546154499 for more information
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Provide optional claims to Azure AD apps - Microsoft Entra
You can use optional claims to: Select additional claims to include in tokens for your application. Change the behavior of certain claims that ......
Read more >Invalidating JSON Web Tokens - Stack Overflow
Add the token version field to the user record. Add the value in this field to the claims stored in the JWT. Increment...
Read more >How to mark required (and optional) fields in a form where ...
The obvious answer would be to use an asterisk to mark the required fields, yet it seems problematic to me since the read-only...
Read more >The Question Mark Makes the Preceding Token Optional
You can make several tokens optional by grouping them together using parentheses, and placing the question mark after the closing parenthesis. E.g.: Nov(ember)?...
Read more >Optional Field Setting Throws Parsing Exception for Variables ...
The offer can be set to valid/invalid states by passing various values in offer request(some optional fields). The security token can be invalid...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
LGTM! Perhaps also adding a
(string) comment
field within that object too to give some context without relying on a url that may decayok - did it this way - just change to red_flags for consistency with the other fields