Skip to content

In-repo API clients send no auth token; will 401 against the now-authenticated API (post-#149) #154

Description

@dmccoystephenson

Summary

Since #149/#150, SecurityConfig requires authentication on all endpoints (.anyRequest().authenticated(), only /actuator/health* and swagger paths are permitAll). However, neither in-repo client SDK sends an Authorization header, so every non-health call will receive 401 Unauthorized:

  • Java: src/main/java/preponderous/viron/services/*Service.java (uses RestTemplate with no bearer token).
  • Python: src/main/python/preponderous/viron/services/*Service.py (uses requests with no auth).

Evidence

  • SecurityConfig.java: .anyRequest().authenticated().
  • grep -rn "Authorization\|Bearer\|token" over both services/ trees returns nothing.

Proposed work

Give both clients a way to attach a bearer token (e.g. a configurable token / token-provider injected into RestTemplate interceptors and the Python requests session), and add tests asserting the header is sent.

Notes

Found during #135 while rebasing onto the #149 auth merge. Pre-existing across all client methods, not introduced by #135.


Filed by Claude on behalf of Daniel Stephenson.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions