I am expanded my user authentication schema to include Browser Fingerprints alongside the user login. I need to add a custom URI handler to each OAuth redirect_uri parameter.
I tried to append the browser fingerprint at the client-side directly onto the OAuth URL in this way
$(document).on('click', '.apple,.facebook,.google', async function(e) {
const target = $(this).attr('class');
get_canvas_audio_fingerprint().then(fp => {
window.location.href = $(this).attr('href').replace(`/auth/${target}`, `/auth/${target}/${fp}`);
});
});
In this scenario target is the OAuth handler which I am redirecting to, into my ExpressJS server.
Originally, in the OAuth redirect_uri section of each Developer Account I set the corresponding handler mysite.com/auth/apple||facebook||google, and that was working fine. Ever since I added the /${fp} to the redirect_uri, I am getting errors in regards to invalid web request uri.
How do I add a custom URI handler support to each OAuth console (Apple, Facebook, Google) to be able to include this additional variable (unique to the user's browser) parameter?
Related questions
Having read this question, I took note of the answer comment
One way to support any provider is that you use a Web flow to redirect to a page on your site and then your website does a redirect to a custom scheme.
Has the OAuth team really not added support for custom response uri's in their API management console?
