3 ms·
> Indeed the goal is to limit the size of JWT tokens. At work we just implemented some M2M auth using JWT[1]. The other party requires a full certificate chain
by magicalhippo 6y ago
> Indeed the goal is to limit the size of JWT tokens.
At work we just implemented some M2M auth using JWT[1]. The other party requires a full certificate chain as our identification and RS256 as algorithm, so our "compact" tokens end up around 8k in size.
At least the auth token we get back lasts a couple of minutes.
[1]: https://difi.github.io/felleslosninger/maskinporten_protocol_jwtgrant.html https://difi.github.io/felleslosninger/maskinporten_protocol...
- rmedaer 6y agoI see that you have a lot of scopes (https://github.com/difi/felleslosninger/blob/ad9ef79b4fef61f741cdfb296ac5f975167f81bf/_docs/ID-porten/oidc/oidc_protocol_scope.md https://github.com/difi/felleslosninger/blob/ad9ef79b4fef61f...). Especially from 3rd parties (https://integrasjon.difi.no/scopes/all https://integrasjon.difi.no/scopes/all https://integrasjon-ver2.difi.no/scopes/all https://integrasjon-ver2.difi.no/scopes/all) Do you have some statistics about that ? For instance, do you know how many scopes are usually requested, on average ?
- magicalhippo 6y agoUnfortunately not. We're just outsiders, using Maskinporten to get an auth token to be used against the REST API of some other gov't agency. For that we use one of two scopes, prod scope or test scope, as they (the agency we talk to) haven't narrowed it down further yet. But if you're interested maybe try to contact the Difi folks running Maskinporten, from my impression there's a high chance there's someone willing to share there. Maskinporten is being phased in as the primary M2M auth solution for any Norwegian gov't agency, so they're bound to get a lot more "users" (agencies), and hence scopes, going forward.