Error while validating (valid) token
See original GitHub issueI run into an issue with token validation. Whenever I do singularity remote login myserver
I simply copy the token from <myserver>/token
. This results in FATAL: while verifying token: error response from server: Invalid Token
. If I check the status with singularity remote status myserver
, I get the following:
SERVICE STATUS VERSION
Keystore Service OK v1.0.0
Library Service OK v1.0.0
Token Service OK v1.0.0
I am using commit 1dc800b8eff66013df59a80c1801847874e11341
of sregistry and singularity v3.3.0 (installed from source) on ubuntu 18.04. Any idea what could be causing this?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Token Validation Error - TIBCO Product Documentation
Token Validation Error ; The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, ...
Read more >How to troubleshoot Intermittent Issue while validating the ...
For a valid token, it throws an error - "Invalid token.". But It accepts the same in subsequent request. PROCEDURE. 1. Turn on...
Read more >Troubleshooting Error While Validating Token (JWT)
Make sure that the JWT made by your server is valid, to check valid or not JWT can check on jwt.io (http://jwt.io/). The...
Read more >Error while validating token using jwt verifier - Questions
I am trying to validate my access token using okta jwt verified , by referring to the link https://github.com/okta/okta-jwt-verifier-java.
Read more >Error Validating Access Token - WordPress.org
An error message “Error validating access token: Session has expire on (date). ... Refreshed tokens are valid for 60 days from the date...
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 Free
Top 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
hey @RonaldEnsing I have a fix for you!
https://github.com/singularityhub/sregistry/pull/251
The issue turned out to be rather silly, and actually I’m not sure why it would behave differently between different timepoints (maybe the client had different capitalization for Bearer?) Basically, I parsed the token header by replacing BEARER with nothing, but the requests coming in now use Bearer. Since we can be sure it’s some version of bearer, a space, and then the token, a clean fix is to split the string by whitespace, and take the second half (the token). Take a look at the PR, let me know if it works for you, and we’ll get this fix in.
Great! I’ll merge the PR.