Always returns isExpired as true. Had to rollback to angular2-jwt to make it work properly.

` isLoggedIn(){ const jwtHelper = new JwtHelperService(); let token = localStorage.getItem(‘token’);

if (!token) {
  
  return false;
  
} else {

  let expDate = jwtHelper.getTokenExpirationDate(token);
  let isExpired = jwtHelper.isTokenExpired(token);

  console.log('Expiration Date',expDate);
  console.log('isExpired',isExpired);

  return !isExpired;
}

}`

[legatek]

This is the commit that changed the behavior quite explicitly:

https://github.com/auth0/angular2-jwt/commit/ce750feddf7073aedc73f024b7fe962471eabcf7#diff-b827188f6870a4e92c47864505a1fd95

The code change appears to be inconsistent with the RFC, in that the exp claim is optional (https://tools.ietf.org/html/rfc7519#section-4.1.4).

Can we get this change reverted?

[atom-morgan]

I’m seeing the same behavior as @srudolph-credera on v.2.0.0.

If a JWT doesn’t have an exp then isTokenExpired always returns true.