Hard to debug OIDC

[iterion]

/about output:

{"version":"v2.3.3","uiVersion":"v2.3.2","commit":"45b06f8","deploymentId":"01K1VQC9BW89NXYNBH918Q8MWT","updateAvailable":false,"latestVersion":null,"llmActive":false,"llmProvider":null,"oidcActive":true,"license":"AGPL-3.0-only","mode":"Distributed (Query)","staging":"/parseable/staging","hotTier":"Enabled, Path: /parseable/hot-tier","grpcPort":8001,"store":{"type":"S3 bucket","path":"sorry-not-here"},"analytics":{"clarityTag":null}}

Description:

I suspect I've made a mistake with my OIDC config, but it's really hard to debug because I'm pretty sure any errors are getting swallowed here:

parseable/src/handlers/http/oidc.rs

Lines 160 to 165 in 17ef955

	let oidc_client = Data::into_inner(oidc_client);
	let Ok((mut claims, user_info)): Result<(Claims, Userinfo), anyhow::Error> =
	request_token(oidc_client, &login_query).await
	else {
	return Ok(HttpResponse::Unauthorized().finish());
	};

I'd expect that parseable would log those errors in some way, it's fine if they're not returned to the end-user, but there should be some way to log them to stdout or even to parseable itself such that you can debug your OIDC config.

[iterion]

I updated to 2.4.0 and I still have the same issue.

[nikhilsinhaparseable]

@iterion thanks for reporting the issue, definitely it has nothing to do with the version.
In order to understand the issue better, will it be ok for you to join the slack and have a chat - https://logg.ing/community
or set up a call here - https://cal.com/nikhilsinha/30min

[iterion]

Thanks, I joined the slack!

[thenodon]

@iterion - what is your oidc IDP? I working to try to get Microsoft ADFS to work , and the problem with ADFS its behaving in a bit of none standard oidc way - of course.