Skip to content

BUG: add Kafka auto-configuration for MFA assurance publisher #247

Closed
digital-bank-java/mfa-service
#18

Description

@ramioooz

Problem

After the SIT assurance publisher was enabled by mfa-service#17, the MFA pod fails during startup because KafkaTemplate is not available for MfaAssuranceMessageSender.

Parent and Sprint

  • Parent: #208
  • Sprint: Sprint 4 - Secure Customer Access and Step-Up Authorization
  • Service: mfa-service
  • Priority: P0

Scope

  • Add the Spring Boot Kafka starter required by the existing assurance publisher.
  • Preserve the existing SIT Helm configuration from mfa-service#17.
  • Verify the service starts with the SIT Kafka broker and the assurance publisher enabled.
  • Do not add a second Kafka configuration, public route, database mutation, or redundant test suite.

Acceptance Criteria

  • KafkaTemplate is auto-configured when assurance publishing is enabled.
  • MFA Service rolls out 1/1 Ready in digital-bank-sit.
  • Startup logs show the assurance publisher is initialized without a missing-bean failure.
  • Existing Maven, Helm, and container checks pass.

Related

Activity

  1. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Corrective implementation

    Pull request mfa-service#18 contains the corrective implementation.

    The merged MFA SIT configuration exposed two runtime defects during rollout:

    • the raw spring-kafka dependency did not provide Spring Boot Kafka auto-configuration, so the assurance publisher could not create KafkaTemplate;
    • PostgreSQL could not infer Instant SQL parameters in the assurance outbox poller and update statements.

    The fix replaces the dependency with spring-boot-starter-kafka and binds all outbox timestamps as JDBC Timestamp values.

    Verification

    • Existing ./mvnw --batch-mode --no-transfer-progress verify -q passed.
    • SIT image digital-bank-java/mfa-service:0.0.5 built successfully.
    • Helm release upgraded successfully.
    • Deployment is 1/1 Ready with zero restarts.
    • /actuator/health returned UP.
    • Startup and scheduled publisher logs remained free of the PostgreSQL outbox binding error after rollout.

    Issue remains open until PR #18 is reviewed and merged, then the permanent image release can replace the temporary SIT tag.

  2. self-assigned this
    on Sep 6, 2026
  3. ramioooz commented on Sep 6, 2026

    @ramioooz
    MemberAuthor

    Post-merge SIT closeout

    Corrective PR mfa-service#18 is merged.

    • Built merged main as digital-bank-java/mfa-service:0.0.6.
    • Helm release upgraded successfully in digital-bank-sit.
    • Current deployment is 1/1 Ready.
    • /actuator/health returned UP.
    • Kafka assurance publisher configuration is enabled and the in-cluster broker is configured.
    • No Kafka template startup failure or PostgreSQL outbox timestamp binding error appeared after the successful restart.

    The first pod restart was caused by a transient Config Server HTTP 500 during rollout; the replacement pod started successfully and remains healthy. The broader MFA assurance story remains open for end-to-end transfer acceptance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions