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

Refactor the access token flow to terminate for ERROR or FAILED action execution status #21383

Closed
2 tasks done
Assignees
Labels
backend identity-core Identity runtime and core development Type/Improvement
Milestone

Comments

@Shenali-SJ
Copy link
Contributor

Shenali-SJ commented Oct 16, 2024

Description

The external service engaged in the action flow serves as an extension of the product. Upon the action execution, the external service is expected to send 3 response statuses namely, SUCCESS, ERROR, and FAILED.

  • SUCCESS: Denotes that the external service successfully processed the request.
  • ERROR: Denotes that the external service encountered a client or server error while processing the request.
  • FAILED: Denotes that the external service declined the request following logical evaluation.

Considering that the external service which serves as an extension, is integrated as part of the overall product offering, the access token flow should be terminated if the action execution is unsuccessful.

Task List

  • Update access token flow based on ERROR status
  • Update access token flow based on FAILED status
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment