Login redirect should respect /?next= queryparam

[AlmerCarbonEquity]

When you login using a passkey, it should take you to the page you originally tried to visit. Workaround I use is to store it in the session and override the get_success_data method from CompleteCredentialAuthenticationView to retrieve it.

[Stormheg]

@AlmerCarbonEquity it is not documented, but this already is a feature. Except it looks for a hidden next input on the page instead of a URL parameter. I agree with you that it should also look out for a next parameter in the URL. Not sure which on should takes precedence, let's see what Django does and replicate that.

django-otp-webauthn/client/src/auth.ts

Lines 320 to 327 in dd5a3aa

	// Find out if there is a hidden 'next' field on the page
	const next = document.querySelector(
	"input[name='next']",
	) as HTMLInputElement;
	let completeAuthenticationUrl = config.completeAuthenticationUrl;
	if (next && next.value) {
	completeAuthenticationUrl += `?next=${encodeURIComponent(next.value)}`;
	}

and

django-otp-webauthn/client/src/auth.ts

Lines 110 to 117 in dd5a3aa

	// Find out if there is a hidden 'next' field on the page
	const next = document.querySelector(
	"input[name='next']",
	) as HTMLInputElement;
	let completeAuthenticationUrl = config.completeAuthenticationUrl;
	if (next && next.value) {
	completeAuthenticationUrl += `?next=${encodeURIComponent(next.value)}`;
	}

(also a good opportunity to de-duplicate this code and extract it into it's own utility function)

Feel free to open a pull request