Roman Štrobl

Operations are expired individually. Surely, this can be optimized. The method `expireOperations` currently expires individual operations by calling the `expireOperation` method: https://github.com/wultra/powerauth-server/blob/3c959a108b9c3c917868059d240036fe762eac4c/powerauth-java-server/src/main/java/io/getlime/security/powerauth/app/server/service/behavior/tasks/v3/OperationServiceBehavior.java#L576 Fix of this issue should improve the performance...

Add tracking for IP address and user agent and store this information in `additionalData` in operations.

Failing test testEncryptionAndDecryptionDifferentActivationFailServerPrivateKeyConverter

1

Log message: ``` ServerPrivateKeyConverterTest.testEncryptionAndDecryptionDifferentActivationFailServerPrivateKeyConverter:78 Expected io.getlime.security.powerauth.app.server.service.exceptions.GenericServiceException to be thrown, but nothing was thrown. ```

Null pointer exception for ApplicationEntity.getRid()

2

Log: ``` java.lang.NullPointerException: Cannot invoke "io.getlime.security.powerauth.app.server.database.model.entity.ApplicationEntity.getRid()" because "this.application" is null at io.getlime.security.powerauth.app.server.database.model.entity.MasterKeyPairEntity.toString(MasterKeyPairEntity.java:237) ~[classes/:1.5.0-SNAPSHOT] ```

Java 15 reports missing JavaDoc for any method as a warning.

Handle null values in converters

2

We should handle null values in converters consistently to avoid issues from static analysis tools. Null value should be checked before entering the switch statement.

We need to prepare documentation for handling large data sizes using partition.

Activation expiration can lead to a deadlock on MSSQL

2

When a concurrent update occurs due to activation expiration, this situation can lead to a deadlock on MSSQL, similar to the situation described in issue https://github.com/wultra/powerauth-server/issues/1609. Deadlock scenario: * UPDATE...

When registering an authenticator, use credential ID from attestation object instead of the registration request. The `credentialId` value in registration request seems duplicate and the value from attestation object is...

### Description Token digest calculation should use `KMAC-256`. ### Acceptance criteria _No response_ ### Technical specification _No response_ ### QA specification _No response_