-
Notifications
You must be signed in to change notification settings - Fork 8
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
SA jwt can not unmarshal .exp field #187
Comments
desimone
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Dec 30, 2022
I made a simple test and I cannot reproduce the issue. rnd := rand.New(rand.NewSource(1))
key, err := ecdsa.GenerateKey(elliptic.P256(), rnd)
require.NoError(t, err)
signer, err := jose.NewSigner(jose.SigningKey{Algorithm: jose.ES256, Key: key}, nil)
require.NoError(t, err)
jws, err := signer.Sign([]byte(`{"exp": 1672319325}`))
require.NoError(t, err)
sig, err := jws.CompactSerialize()
require.NoError(t, err)
cred, err := parseToken(sig)
if assert.NoError(t, err) {
assert.NotNil(t, cred)
} I'm not sure where the error is occurring. |
desimone
added
the
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
label
Jan 4, 2023
This should be fixed in Pomerium v0.22.3 or later (see pomerium/pomerium#4149). |
kenjenkins
removed
blocked
PR/ISSUE is blocked by third party
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
labels
Aug 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to use SA jwt via cli version 0.21.0-beta
Getting:
decrypted jwt (second part)
The text was updated successfully, but these errors were encountered: