dotnet/aspnetcore

Log decryption failures

Open

#4,651 opened on Jun 1, 2018

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)C# (10,653 forks)batch import
affected-mediumarea-authenhancementhelp wantedseverity-minor

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (PR metrics pending)

Description

"Correlation failed" is one of the most common failures in OIDC or OAuth flows. Many of the things that can go wrong here happen on the client and can't be traced from the server. However there's one scenario where everything does flow back to the server and the server fails to decrypt the values. This can happen in a multi-node environment with misconfigured dataprotection (RE: https://github.com/aspnet/Security/issues/1755). We can highlight this by logging decryption failures in OAuth, OIDC, and CookieAuth.

Contributor guide

Research direction
Add logging statements in the OAuth, OIDC, and Cookie authentication handlers to log decryption failures, specifically when data protection decryption fails due to misconfigured keys in multi node environments.
Tech stack
csharp
Domain
backendsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65