The MIW provides a /token endpoint which is meant to operate with the existing iatp flow. The current implementations of the iatp only allow the usage of application/x-www-urlencoded http bodies. The current implementation of the MIW only accepts a json body. This difference should be fixed on the MIW side by either:
Accepting the additional body type and the existing JSON type
-OR- only accepting the new body type
Both solutions are valid, and whichever causes the least amount of refactoring can be chosen.
Acceptance Criteria
[ ] The application endpoint /token accepts and processes an x-www-formurlencoded body.
Description
The MIW provides a
/tokenendpoint which is meant to operate with the existing iatp flow. The current implementations of the iatp only allow the usage ofapplication/x-www-urlencodedhttp bodies. The current implementation of the MIW only accepts ajsonbody. This difference should be fixed on the MIW side by either:Both solutions are valid, and whichever causes the least amount of refactoring can be chosen.
Acceptance Criteria
/tokenaccepts and processes anx-www-formurlencodedbody.