Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add tp scheme adapter snippets. clarify auth wording #22

Merged
merged 6 commits into from
Sep 16, 2020

Conversation

kleyow
Copy link
Contributor

@kleyow kleyow commented Sep 10, 2020

  • add more snippets from the tp-scheme-adapter
  • move away from "Auth" as a naming to avoid confusion between Authorization and Authentication (please double check that the are named correctly 😅 )

Copy link
Contributor

@lewisdaly lewisdaly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Kevin - this is important to clean up and make easier to understand.

Here's some suggestions for naming conventions that might make things simpler:

  • we should try to avoid the term Authorization(s) in the thirdparty-api where possible - and keep Authorization(s) for the FSPIOP-API methods/objects etc. that we copied across
  • For auth stuff related to Consents or ConsentRequests, maybe we can use Consent or Consent Request (e.g. ConsentRequestChannelType instead of AuthorizationChannelType

docs/thirdparty-openapi3-snippets.yaml Outdated Show resolved Hide resolved
thirdparty/openapi3/schemas/AuthenticationType.yaml Outdated Show resolved Hide resolved
thirdparty/openapi3/schemas/AuthorizationStateType.yaml Outdated Show resolved Hide resolved
docs/thirdparty-openapi3-snippets.yaml Outdated Show resolved Hide resolved
docs/thirdparty-openapi3-snippets.yaml Outdated Show resolved Hide resolved
docs/thirdparty-openapi3-snippets.yaml Outdated Show resolved Hide resolved
docs/thirdparty-openapi3-snippets.yaml Outdated Show resolved Hide resolved
@kleyow
Copy link
Contributor Author

kleyow commented Sep 10, 2020

Thank you for clarifying and expanding on this Lewis. Glad we are ironing this out.

Copy link
Contributor

@eoln eoln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scheme related interfaces are dedicated to synchronous operations (especially Outbound interfaces) which are merging gathering responses from asynchronous flows driven by state machines. They should be separated from core Switch interfaces. But the Scheme Inbound interfaces should match exactly the core Switch interfaces which should be implemented by DFSP/Thridparty

chore: address comments

chore: fix example

chore: remove property
@kleyow
Copy link
Contributor Author

kleyow commented Sep 14, 2020

Scheme related stuff removed.

Copy link
Contributor

@eoln eoln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, but let wait on @lewisdaly before merge -> please take a look here also: mojaloop/pisp-project#66

properties:
challenge:
type: string
description: The original Challenge Object as a JSON string
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we shouldn't use JSON.stringify as stringify method because it can generate non-identical strings, there is a need for additional design decision see: mojaloop/pisp-project#66

@kleyow
Copy link
Contributor Author

kleyow commented Sep 16, 2020

The issue has been bubbled up to design. Going to merge this since it's blocking swagger documentation.

@kleyow kleyow merged commit 2ca0bc4 into mojaloop:master Sep 16, 2020
@kleyow kleyow deleted the chore/more-snippets branch September 16, 2020 03:51
@HenkKodde
Copy link

HenkKodde commented Sep 16, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants