Summary
Field report: Axis cameras return sender not authorized SOAP fault with current build. Older build (252.2) works fine against the same camera.
Confirmed present in the latest released build — NOT introduced by Sprint 6.
Symptoms
- Connection succeeds (GetCapabilities works)
- Media operations (GetProfiles, GetStreamUri, etc.) return SOAP FaultException with auth error
- Likely
wsse:FailedAuthentication or similar SubCode
Investigation status
- Diagnostic logging added to
feat/media2-support branch (Sprint 6) covering UpgradeScheme, SetupUserNameToken, withMedia1/2HttpFallback, channel creation
- FaultException is NOT caught by the HTTP fallback (correct — only connection-refused triggers fallback)
- Fallback channels confirmed to have SetupUserNameToken applied
- Primary channel (HTTPS-upgraded URL from UpgradeScheme) is the one failing auth
Next step
Connect Axis camera as fleet member, collect TRACE logs, check:
- What URL UpgradeScheme produces for the Axis media service
- Whether WCF WS-Security token is accepted on that endpoint
- Compare with 252.2 behavior
Affects
- All Axis cameras in field
- Severity: HIGH (camera unusable)
Summary
Field report: Axis cameras return
sender not authorizedSOAP fault with current build. Older build (252.2) works fine against the same camera.Confirmed present in the latest released build — NOT introduced by Sprint 6.
Symptoms
wsse:FailedAuthenticationor similar SubCodeInvestigation status
feat/media2-supportbranch (Sprint 6) covering UpgradeScheme, SetupUserNameToken, withMedia1/2HttpFallback, channel creationNext step
Connect Axis camera as fleet member, collect TRACE logs, check:
Affects