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
User/mmi/43308 failure scen repair #210
Conversation
doc/general/cash-register-integration/cash-register-integration-failure-scenarios.md
Show resolved
Hide resolved
doc/general/cash-register-integration/cash-register-integration-failure-scenarios.md
Outdated
Show resolved
Hide resolved
doc/general/cash-register-integration/cash-register-integration-failure-scenarios.md
Outdated
Show resolved
Hide resolved
![](./images/09-end-late-signing-mode.png) | ||
|
||
#### Failure of the Signature Creation Unit | ||
If the communication to the secure Signature Creation Device fails, the POS System can continue to operate until the SSCD is accessible again. Receipts created in a state where no communication is possible with the SSCD device are protected by the security mechanism of fiskaltrust.The fiskaltrust.Middleware will respond with the ftState = 0x02 "SSCD communication failed". The POS System receives the response and processes the data it contains. For following Requests no more communication attempts are done to avoid long waiting times for each Receipt request/Receipt response sequence. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might make sense to only speak about "SCU" here and not mix it with SSCD, e.g. like that:
"If the communication to the SCU fails (e.g. when the secure Signature Creation Device is not reachable), ..."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also:
If the communication to the secure Signature Creation Device fails, the POS System can continue to operate until the SSCD is accessible again. Receipts created in a state where no communication is possible with the SSCD device are protected by the security mechanism of fiskaltrust.The fiskaltrust.Middleware will respond with the ftState = 0x02 "SSCD communication failed". The POS System receives the response and processes the data it contains. For following Requests no more communication attempts are done to avoid long waiting times for each Receipt request/Receipt response sequence. | |
If the communication to the secure Signature Creation Device fails, the POS System can continue to operate until the SSCD is accessible again. Receipts created in a state where no communication is possible with the SSCD device are protected by the security mechanism of fiskaltrust. The fiskaltrust.Middleware will respond with the ftState = `0x02` "SSCD communication failed". The POS System receives the response and processes the data it contains. For following Requests no more communication attempts are done to avoid long waiting times for each Receipt request/Receipt response sequence. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might make sense to write a paragraph about the failed mode and why we introduced it (the "official" pattern is called "circuit breaker")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added failed-mode/circuit breaker explanation
doc/general/cash-register-integration/cash-register-integration-failure-scenarios.md
Outdated
Show resolved
Hide resolved
…n-failure-scenarios.md Co-authored-by: Tom Schmiedlechner <TSchmiedlechner@users.noreply.github.com>
…n-failure-scenarios.md Co-authored-by: Tom Schmiedlechner <TSchmiedlechner@users.noreply.github.com>
created new failure scenario page with more detailed explanation