Project in Visual Studio .NET Core with token authentication and api.
Budget: $30 – $250 USD
I need a web site project in Visual Studio 2019, .NET Core 5, MVC.
With token authentication:
when user log in the token provided, then requests are identified and user identity is available in User object in controller method.
Users are stored in DB MS SQL SERVER 2019 User ID must be uid nvarchar(128);
Also web api methods are needed:
Register user, Log in, Log out, Remind password, Change password, Change email.
When user registeres he enter only email, then recieve email with temporary password and login link.
He clicks link and is redirected to website and log in automatically and user account is activated.
In Remind password method - new temporary password is created and sent to email.
Tokens must be endless and store in database (stored hashes of tokens) so:
users will be authenticated untill they do log out;
many devices can log in to same account - and have different tokens because only hash of token is stored in DB. With another log in new token is generated.
When user logs off, all tokens must be cleared.
All operations: register, log in, log out, change password, change email save in log table in DB.
The DB context has name AuthContext beacause later will be another context for other data.
No real email send needed: all methods needed only in API so all can be tested in Postman.
With token authentication:
when user log in the token provided, then requests are identified and user identity is available in User object in controller method.
Users are stored in DB MS SQL SERVER 2019 User ID must be uid nvarchar(128);
Also web api methods are needed:
Register user, Log in, Log out, Remind password, Change password, Change email.
When user registeres he enter only email, then recieve email with temporary password and login link.
He clicks link and is redirected to website and log in automatically and user account is activated.
In Remind password method - new temporary password is created and sent to email.
Tokens must be endless and store in database (stored hashes of tokens) so:
users will be authenticated untill they do log out;
many devices can log in to same account - and have different tokens because only hash of token is stored in DB. With another log in new token is generated.
When user logs off, all tokens must be cleared.
All operations: register, log in, log out, change password, change email save in log table in DB.
The DB context has name AuthContext beacause later will be another context for other data.
No real email send needed: all methods needed only in API so all can be tested in Postman.