ASP.NET CORE Client-Side Best Practice to pass to Generate the Token.
The API has been configured with a JWT to secure few actions (e.g. PUT).

I have enabled the Edit link (in the index.cshtml) that navigates to a razor page with a form that gets populated. Then user makes some changes and clicks submit button. So now I need to secure this.

Secure the Edit so only people with the token can access the form?

Secure the “submit button” instead?

Although it might be a design preference, I am looking for best-practice to implement token functionality on the client side.

Do I approach it similarly to the API (green Authorized button with lock )?
Any help will be appreciated