Always exchange to Altinn token when communicating with Altinn platform #167
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We previously used Maskinporten token to Altinn Authorization, but that is no longer the case. Hence we move exhangeToAltinnToken to "global" configuration for our Altinn services.
There seems to have been an issue with cache invalidation where the authorization token, which was Maskinporten only, was not renewed as expected. Reading through the library, it does not seem like how we used the library (doing both Maskinporten and Altinn token at the same time) was the expected way to use it. Nor is it the way forward for us either.
Related Issue(s)
Verification
Documentation