adorsys / adorsys/open-banking-gateway
Consent matching
- 主要言語
- Java
- スター
- 338
- フォーク
- 122
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
Match already existing consent by request parameters
- [ ] ValidationInfo annotation (fields to be filled that are shown to the user) should be configurable on bank-level and consent authorization mode (EMBEDDED/REDIRECT) in the database. Default is mandatory when nothing in DB. This means that fields like ASPSP ID can be made optional or mandatory per bank based on the selected authorization approach. I.e. `2131-1243-13443-4344 : {PSU_ID: {EMBEDDED: MANDATORY, REDIRECT: NOT_REQUIRED}}`
- [ ] Define consent class for Xs2a protocol that will be used for consent sharing
- [ ] Consent matching for list accounts supporting global consent (i.e. allPsd2) and dedicated consent (i.e. for IBAN 12345 consent for `allPsd2: allAccounts` should match)
- [ ] Consent matching for list transactions supporting global consent (i.e. allPsd2) and dedicated consent (i.e. for IBAN 12345 consent for `allPsd2: allAccounts` should match)
- [ ] Consent conflict resolution (see https://app.zenhub.com/workspace/o/adorsys/open-banking-gateway/issues/519)
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
評価
この issue はまだ評価されていません。