Encrypted request parameter `fipid` description is not compliant to standard `application/x-www-form-urlencoded` format - Githubissues

Sahamati / aa-redirection-guidelines

Guidelines for interaction between FIU and AA on the user’s device.

https://sahamati.gitbook.io/aa-redirection-guidelines

Apache License 2.0

6 stars 9 forks source link

Encrypted request parameter `fipid` description is not compliant to standard `application/x-www-form-urlencoded` format #12

Closed dheerajkhardwal closed 1 year ago

dheerajkhardwal commented 1 year ago

https://github.com/Sahamati/aa-redirection-guidelines/blob/ca8b8dd15e1d39b31b9ef4bc25d226485eade02d/specification/request-specification.md?plain=1#L29

Ambiguous text:

then they can pass this info to AA as a comma separated array in curly braces

The ecreq parameters are expected in standard application/x-www-form-urlencoded format. Thus for supplying multiple FIP identifiers, the format should be &fipid=XXXX&fipid=YYYY.

dheerajkhardwal commented 1 year ago

Closed by #13