Hard-coding the JWT is not ideal, library-clients should be able to set this to whatever they like. It would be most-useful to set it from a ConferenceConfig which is loaded from JSON.
A multi-year conference, like MozFest, would like to set the JWT ISS to mozfest-2022 so that the client can discard tokens that are for the previous year's conference. This is because the conference is hosted on the same domain but JWTs that users have already stored are incompatible.
Hard-coding the JWT is not ideal, library-clients should be able to set this to whatever they like. It would be most-useful to set it from a
ConferenceConfig
which is loaded from JSON.A multi-year conference, like MozFest, would like to set the JWT ISS to
mozfest-2022
so that the client can discard tokens that are for the previous year's conference. This is because the conference is hosted on the same domain but JWTs that users have already stored are incompatible.