| swagger: '2.0' | |
| info: | |
| version: v1 | |
| title: SxS Events | |
| description: 'Events described here tell you what happens during the use of **tokens** to authenticate users and confirm transactions.' | |
| contact: | |
| name: Igor Vlahek | |
| email: igor.vlahek@asseco-see.hr | |
| { | |
| "type": "object", | |
| "required": [ | |
| "openapi", | |
| "info", | |
| "paths" | |
| ], | |
| "properties": { | |
| "openapi": { | |
| "type": "string", |
| swagger: '2.0' | |
| x-asee-visibility: public | |
| info: | |
| description: Multifactor Authentication API enables authentication of users and signing of sensitive transactions using token based credentials or random one-time verification code sent to pre-registered email account or mobile number. Authentication and signatures using token based credentials follow OATH standard HOTP, TOTP and OCRA algorithms or their proprietary alternatives. Initiation of out-of-band authentication and signature flows is possible with images (QR code) and push messages. | |
| title: Multifactor Authentication API | |
| version: beta | |
| host: bankapi.net | |
| basePath: /beta/mfa | |
| tags: | |
| - description: One-time code to verify proof of control over phone number or email address |
| { | |
| "type": "object", | |
| "required": [ | |
| "openapi", | |
| "info", | |
| "paths" | |
| ], | |
| "properties": { | |
| "openapi": { | |
| "type": "string", |
| /* | |
| Utility code for Sleuth submissions | |
| =================================== | |
| Author: Aleksandar Milosevic | |
| License: Creative Commons CC BY 4.0 | |
| Utility provides visual aids for Sleuths submissions | |
| - displays mouse pointer x and y position | |
| - displays candidate line when considering next vertex |
| # OpenAPI version identifier - required for OpenAPI 3.0 domains | |
| openapi: 3.0.0 | |
| ####################### | |
| # Optional info section | |
| ####################### | |
| info: | |
| title: Acme Components | |
| description: Common components for Acme REST APIs |
| openapi: 3.0.3 | |
| info: | |
| title: Adaptive Cards | |
| description: This is a port of Adaptive Cards schema to swagger editor for exploration | |
| version: 1.3.0 | |
| paths: {} | |
| components: | |
| schemas: | |
| AdaptiveCard: |
In the context of distributed systems orchestration, a Saga Execution Coordinator (SEC) is defined as a centralized, persistent Finite State Automaton (FSA). Its purpose is to manage the integrity of a distributed transaction by enforcing a strict execution path across a pre-ordered sequence of local transactions and their corresponding inverse operations (compensations).
Let a Saga