Skip to content
OAuth callback authorization codes in internal Railway logs
Anonymous
OP

16 days ago

Does Railway capture OAuth callback query strings containing temporary authorization codes, such as LinkedIn OAuth codes, in any internal edge, proxy, security, diagnostic, tracing, or error logs, even when application logging excludes them?

If so, are the code values redacted before storage, what retention periods and access controls apply, and which subprocessors can receive them? Are there supported settings to prevent these values from being retained?

This is a generic architecture question. No real credentials, callback URLs, or account details are included.

Solved

1 Reply

Railway
BOT

16 days ago

Our HTTP access logs record the URL path without query parameters, so a request to /callback?code=... is stored as /callback and the authorization code isn't included. Request traces we generate also exclude query parameters. Those HTTP logs do record the client IP, User-Agent, method, host, status and timing, but not the full set of request headers or raw cookie values.

Query strings can still end up stored if your application writes them. That covers full URLs printed to stdout/stderr, which become your service logs, and OpenTelemetry traces your app sends that include full URLs or query parameters.

Logs are kept for up to 90 days. Your plan's retention figure (7 days on Hobby) only controls how far back you can view them. Individual log entries can't be redacted or deleted early, and there's no setting to change what gets retained, so the control you have is not emitting these values from your application.

For subprocessors and contractual terms, see our subprocessor list and DPA.


Status changed to Awaiting User Response Railway • 16 days ago


Railway
BOT

8 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 8 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...