New answers tagged

4

Yes its unethical, you are wasting their time. But its also impractical. You can only do it once or twice before they stop talking to you. The price they offer will reflect their business model and might not work for you. Ie they might sell stuff cheap to drag customers into another product The price they offer you wont be the same as the one they offer ...


2

First off, the token approach seems sound for your case. One option is to encrypt user information (e.g. id) into the token. On the server side, you can then keep things stateless. Realize that no matter the details of how it is generated, this token is sensitive. If someone has it, they can use it to pretend to be that user as long as it is valid (just ...


1

Don't really know the full use case but this really screams using a session to me. Normally these are implemented with a unique ID sent to the client in the form of a cookie and stored on the server in an in memory database like redis or memcached. When a user logs a new object will be added to redis and stored by a unique key with any user information ...



Top 50 recent answers are included