Once upon a time in the CLC, the ID token was the only JWT known. The CLC has the payload for the ID token as a JSON object, which means that code is littered with direct access to it for information like expiration time etc. In the mean time, JWTs got their own spec and there is now very nice machinery in the rest of OA4MP to deal with JWTs. Therefore, convert the CLC to use one of these rather than the ever more clunky direct access.
This should not change functionality at all, but will centralize a lot of operations and just make the code less of a mess.
Once upon a time in the CLC, the ID token was the only JWT known. The CLC has the payload for the ID token as a JSON object, which means that code is littered with direct access to it for information like expiration time etc. In the mean time, JWTs got their own spec and there is now very nice machinery in the rest of OA4MP to deal with JWTs. Therefore, convert the CLC to use one of these rather than the ever more clunky direct access.
This should not change functionality at all, but will centralize a lot of operations and just make the code less of a mess.