How to design a acess_token mechanism?

To verify the validity of the user
Need to add a acess_token mechanism

The little brother didn't want to know how to store this thing?

If user a asks for the first time to assign him a acess_token = a (denoted by a). Then put this a and build time into the database?

Then user a next time to verify from the database to query whether a is expired? Return an error code if it expires? Is this the path? Ask for advice

Reply to discussion (solution)

Can be passed by cookie, form hidden field, url parameter, or embedded in API
Whether you want to store it in a database depends on the lifetime of your token
Tokens are usually used as a supplement to a cookie or session and are issued temporarily

Can be passed by cookie, form hidden field, url parameter, or embedded in API
Whether you want to store it in a database depends on the lifetime of your token
Tokens are usually used as a supplement to a cookie or session and are issued temporarily
Thank you for your reply. I'm going to make an API interface.
I'll think again!

What kind of storage mechanism is acess_token in a similar API?
Do you know anything about that, thank you.

This acess_token is generally issued temporarily (after successful login)
The General API user is large, the issued Acess_token contains the time information
You don't have to bother with the database.

