Update REST API with support for IDPorten tokens from new test issuer environment #726
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…/environment Updates `IdPortenWellKnownConfigEndpoint` and `IdPortenAlternativeWellKnownConfigEndpoint` to the use `idporten.no` domain. See Altinn#254 for details.
|
This issue is currently blocking 3rd party developers from using the altinn 3 sluttbruker api with tokens from idporten (which seems to be the recommended solution for web-apps in the docs). Alternative approaches or workarounds would also be appreciated 🙂 |
TheTechArch
approved these changes
Oct 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Changes the
IdPortenWellKnownConfigEndpointandIdPortenAlternativeWellKnownConfigEndpointfrom using thedifi.nodomain toidporten.nodomain.Related Issue(s)