-
Notifications
You must be signed in to change notification settings - Fork 11
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
Add column for signature metadata #971
Labels
Comments
jandusil
added a commit
that referenced
this issue
Aug 24, 2023
- Add new column signature_metadata, remove merged columns signature_data_method and signature_data_uri_id, document it in liquibase - Edit entity class, introduce new converter
jandusil
added a commit
that referenced
this issue
Aug 29, 2023
- Make the change retrospective in terms of liquibase
jandusil
added a commit
that referenced
this issue
Aug 30, 2023
- Introduce abstraction for SignatureMetadata
jandusil
added a commit
that referenced
this issue
Aug 30, 2023
- Add a test - Introduce more generic approach
jandusil
added a commit
that referenced
this issue
Aug 30, 2023
- Add a test - Introduce more generic approach
jandusil
added a commit
that referenced
this issue
Sep 5, 2023
- Change type of signature_metadata to clob - Incorporate code review comments
jandusil
added a commit
that referenced
this issue
Sep 6, 2023
* Fix #971: Add column for signature metadata - Add new column signature_metadata, remove merged columns signature_data_method and signature_data_uri_id, document it in liquibase - Edit entity class, introduce new converter - Propagate changes - Introduce abstraction for SignatureMetadata - Add tests
A follow-up to #500 |
banterCZ
added a commit
that referenced
this issue
Sep 11, 2023
Document signature_metadata db column
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PowerAuth server should support mutliple signature types, hence columns
signature_data_method
andsignature_data_uri_id
in tablepa_signature_audit
should be generified into a single JSON column e.g.signature_metadata
.Sample structure of contents of column
signature_metadata
after migration to JSON format:Other signature types will use dedicated JSONs. Let's prepare classes which model various signature types, for this release only the PowerAuth signature model class type.
The text was updated successfully, but these errors were encountered: