Why must the route, envelope DSN, and Sentry authentication credentials agree? #63
|
How does Bicho authenticate Sentry requests when credentials appear in more than one place? Can an envelope DSN still name the old Sentry host? |
Replies: 1 comment
|
Bicho accepts protocol-v7 query authentication, For query authentication, the request supplies When several credential sources are present, all supplied keys and secrets must agree, and the key must belong to the project named in the route. Duplicate authentication fields can also cause rejection. Adding a valid header does not override a stale query key or envelope DSN. An envelope DSN must use the receiving installation's origin and exactly identify the route project. A DSN naming the old Sentry host is invalid even if the request reaches Bicho through a tunnel. Bicho does not forward ingestion to that host. Secret-enabled projects still require their ingest secret, normally through Documentation - Move from Sentry Source - Bicho: Sentry ingestion |
Bicho accepts protocol-v7 query authentication,
X-Sentry-Auth, or an envelope header containing a DSN. The ingest route isPOST /api/:project_id/envelope, or/storefor raw legacy JSON. Both routes accept a trailing slash. A route project ID by itself is not authorization.For query authentication, the request supplies
sentry_version=7andsentry_key. A header uses the Sentry authentication syntax, for example:When several credential sources are present, all supplied keys and secrets must agree, and the key must belong to the project named in the route. Duplicate authentication fields can also cause rejection. Adding a v…