You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to a variability of Crypto4 protocol, we need to refactor multiple internal components of PowerAuthCore module, written in C++. Internally, Session object should no longer implement all heavy protocol stuff, such as authorization code calculation. We should offload this to separate interfaces and specific implementations, depending on the protocol version and selected algorithms.
The best example is SharedSecret interface that defines algorithm independent process for a for key-agreement.
Acceptance criteria
No response
Technical specification
No response
QA specification
No response
JIRA issue code
No response
The text was updated successfully, but these errors were encountered:
It would be nice to use this new approach also for SDK v 1.10.0. So, we should refactor the core first, then implement interfaces with protocol V3.3 and after that we should build crypto4 on top of this foundation.
Description
Due to a variability of Crypto4 protocol, we need to refactor multiple internal components of PowerAuthCore module, written in C++. Internally, Session object should no longer implement all heavy protocol stuff, such as authorization code calculation. We should offload this to separate interfaces and specific implementations, depending on the protocol version and selected algorithms.
The best example is
SharedSecret
interface that defines algorithm independent process for a for key-agreement.Acceptance criteria
No response
Technical specification
No response
QA specification
No response
JIRA issue code
No response
The text was updated successfully, but these errors were encountered: