Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*"
Favorites infavorites:mine
Status closed:yes
Types is:question
Exclude -[tag]
For more details on advanced search visit our help page
Results tagged with Search options answers only user 222996

Authentication is the act of one entity proving its identity to another entity. Common examples involve public key cryptography. For example, proving that a banking web site actually belongs to the bank you think it does.

at the same time on both sides of the system (client and server). How should I implement authentication in this scenario? Be consistent, treat all clients equally, so that you can reuse the same …
answered Jan 23 by Laiv
depends on the needs, but yes, that's a fairly common implementation. However, it has led many people to believe that OAuth2 is an authentication protocol too; when it's not. As an additional … confounder to our topic, an OAuth process does usually include several kinds of authentication in its process: the resource owner authenticates to the authorization server in the authorization step …
answered Sep 16 '17 by Laiv
authentication protocol, so one more reason to leave it aside for now. Anyways, take a look to this article and get your own conclusions and decide if it's suitable for you. The OAuth2 main goal is authorising … and authentication). That's neither right nor wrong. It's just the solution that best serves their needs. You never should implement something just because everyone else does it1. If you do, it's …
answered Jul 15 '17 by Laiv
The short answer is no. From the JWT security point of view, there should not be any problem, since email is an already valid public claim registered in the IANA. On the other hand ... I have a …
answered Sep 7 '17 by Laiv
How would authentication work for example, for an endpoint like /users/1/orders. The JWT token would handle actual access to the API (for the consumers, such as an app or third-party) but how … do we make sure the actual end user has authenticated? Because the end-user have had to go through an authentication process. Such a process, among other things, gave a fresh JWT to the client …
answered Dec 13 '18 by Laiv
if in a monolith MVC application (i.e rails) you have other entry-points than just the Controller? I.e background jobs, or the model interaction? Consider workers (jobs executors) as actors o …
answered Apr 5 by Laiv
Q: 1-2 Yes, it might happen. Hackers can impersonate other users if they managed to steal their authorization tokens. However, it would take them (usually) to get access to the user's client. Regard …
answered Nov 1 '18 by Laiv
. Thresholds Setting a max number of request per second and source (remote address). Let's say X Req/s per IP address. Thresholds are commonly implemented in the API Gateway or in the Authentication … the causes of the error. Making your security opaque to the externals reduces the attack surface. Authentication tokens I would encourage you to don't reinvent the wheel, overall with security. JWT …
answered May 19 '17 by Laiv
authentication/authorization protocols has become a must-have. If we plan to use the Authorization header for all these protocols, we have to make our auth service consistent. The way to communicate what …
answered Jul 20 '17 by Laiv
Is this approach secure? Specifically: Is sending the username and password through JSON safe if done over HTTPS? Yes. Headers, request params and request body are encrypted during the …
answered Jun 30 '17 by Laiv
Cookies: in their early version, a text file with a unique client Id an all the other information needed about the client (e. g. roles) Cookies are tuples key-value originally addressed to reta …
answered Sep 3 '17 by Laiv