I realized that It were because of different algorithm types. spring
resource server uses hmacsha256 default when using symmetric key, but cas
sends hmacsha512. so i updated accessTokenConverter() method like below;
@Bean
public JwtAccessTokenConverter accessTokenConverter() {
Jw
hello, is there anybody that verify jwt with spring resource server? i have
configuration like this. when i use custom oauth2 server, it works well.
but when i change to cas oauth2 server, it cannot verify jwt.
cas oauth2
cas.authn.token.crypto.enabled=true
cas.authn.token.crypto.signing-enable
Hi all,
I got a similar issue when I try to verify the jwt signature with several
libreries including Node.js jsonwebtoken, since the library allows only
base64url encoded tokens because of mentioned RFC7515.
With java-jwt library the token is correctly verified.
Debugging the code i found in c
I think the jwt as seen in the url as the value for the token parameter has
been rul'ized by converting some characters to their html entity values.
If you look at the same jwt as seen in the cas logs you will find it does
not have the html characters, it's pure base64. If I use that value or
I am observing that extra non base64 char are appended to payload. If i
remove them then I am able to verify signature. Can someone suggest if this
is CAS issue or issue in my configurations ?
JWT:eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJpdmVyYXNlIiwiaXNGcm9tTmV3TG9naW4iOiJ0cnVlIiwiYXV0aGVudGljYXRpb25EYXRl
I think you are seeing the discrepancy due to base64 vs. base64url
decoding. I think the jwt spec. wants base64 url vs. plain base64.
https://en.wikipedia.org/wiki/Base64#URL_applications
On Friday, December 14, 2018 at 9:37:45 AM UTC-6, Devendra Sisodia wrote:
>
> While decoding JWT there is
While decoding JWT there is error "Bad Base64 input character decimal 37 in
array position 806" Which means 37(%) is not allowed in encoded base 64
string in JWT.
My JWT looks like below and yellow highlighted is the 806th element that
cannot be base 64 decode.
eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJpdm
i'm using io.jsonwebtoken.jjwt library
Jwts.parser().setSigningKey().parseClaimsJws();
Il giorno venerdì 14 dicembre 2018 14:02:14 UTC+1, Devendra Sisodia ha
scritto:
>
> Hello,
>
> Big Thanks for sharing configuration and as a result JWT is not encrypted
> and only signed.
>
> But now I fa
Hello,
Big Thanks for sharing configuration and as a result JWT is not encrypted
and only signed.
But now I face strange issue. when I try to verify signature it fails. I am
using AES and single key to sign and JWT is generated. But the generate JWT
fails signature verification.
JWT generated as
yes
###Token/JWT Tickets ENCRIPTION
cas.authn.token.crypto.enabled=true
cas.authn.token.crypto.signing-enabled=true
cas.authn.token.crypto.signing.key=
Dkkpi7iUKqidOXXmeAbr4RyHirYmgQgqqUrIo6q_JPNks2iqX2l95jVVoZQDWLNiFnhQF43agCtdMxRnIXOO9g
cas.authn.token.crypto.encryption-enabled=false
cas.aut
Sorry, but this does not work.
How's your service(one with definition of 'jwtAsServiceTicket', etc) looks
like ?
On Thu, Dec 13, 2018 at 2:09 PM Giuseppe Infurna
wrote:
> Hi all,
> I'm work fine with
>
> cas.authn.token.crypto.encryption-enabled=false
> cas.authn.token.crypto.encryption.key=
>
Hi all,
I'm work fine with
cas.authn.token.crypto.encryption-enabled=false
cas.authn.token.crypto.encryption.key=
Il giorno lunedì 12 novembre 2018 16:44:10 UTC+1, Xavier Rodríguez ha
scritto:
>
> I'm configuring Cas Server 5.3.3. In one service I need to response a JWT
> without encryption.
Hi all,
Just to describe in details what is my requirement:
Need JWT signed but without encryption. Tried below config but to no avail:
cas.authn.token.crypto.encryptionEnabled=false
cas.authn.token.crypto.signingEnabled=true
Can some please suggest how this can be achieved ?
On Thu, Dec 13, 20
Hello Xavier, all,
I too have similar requirement of JWT without encryption and wondering if
there exists any solution.
Regards,
Devendra
On Monday, November 12, 2018 at 4:44:10 PM UTC+1, Xavier Rodríguez wrote:
>
> I'm configuring Cas Server 5.3.3. In one service I need to response a JWT
> wi
14 matches
Mail list logo
