How do I prevent resending resend OTP razor page from another browser’s tab?

Question

1.00/5 (1 vote)

See more:

Hi,

I have a razor page called

C#

ForgetPasswordOtp.razor

page with directive

C#

@page "/ForgetPasswordOtp/{UserName}"

. How can I prevent the same page access from another browser tap. It is causing a problem like everyone can access the page and resent the otp again and again. I need to prevent the page from another browser tab. In Index.razor page I already written a below code for prevent back.

What I have tried:

JavaScript

<script>
        function preventBack() { window.history.forward(); }
        setTimeout("preventBack()", 0);
        window.onunload = function () { null };
    </script>

And inside ForgetPasswordOtp.razor page calling the function on

C#

OnInitializedAsync()

C#

protected override async Task OnInitializedAsync()
    {
 await JsRuntime.InvokeVoidAsync("preventBack");
}

Like wise how can I prevent the resend otp page from another browser's tab?

Thanks

Posted 5-Aug-23 4:19am

Rajesh Kumar 2013

Updated 5-Aug-23 11:33am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Graeme_Grant · Accepted Answer · 2023-08-05T11:33:00

Solution 1

You would need to throttle the requests on the server side using a timed cache of the username as it is the only data being passed. Then when the server receives the request, check the cache and either allow the process to continue or return a throttled response.

As you're doing Blazor development, I would look into using Asp.Net Core's Rate limiting middleware in ASP.NET Core | Microsoft Learn[^]

Posted 5-Aug-23 11:33am

Graeme_Grant

Comments

Rajesh Kumar 2013 9-Aug-23 0:45am

Hi, I am trying to find a solution this way Solution Link. Is this a proper solution for me?

Rajesh Kumar 2013 9-Aug-23 4:05am

Yes I can solve the issue by referring the Link