flâneur

Distributed Systems Architecture: Authentication, authorization and ping-pong nonsense. – PRDeving

prdeving.wordpress.com · 2,208 words · saved by 1 readers

In the last post we explored the problems of accepting connections in high concurrency applications. One of the significant points in opting for asynchronous queue-digester-based solutions is, in my opinion, the management of the client-server relationship from the point of view of authentication, authorization, limitations, etc. This reflection did not take long to bring to my mind the hell of authorization flows in distributed systems and how complex (and absurd) they turn out to be. In this article we will try to summarize authorization flows, the complications we have in distributed architectures and what, from my point of view, is an alternative solution to address them once and for all. Starting from the beginning, the concept of “auth” is ambiguous (by design), it refers to two complementary ideas: authentication and authorization. The authentication process […] answer the question “Who is the user?”, while authorization […]“What can that user do?” The authentication process att

9–14 minutes In the last post we explored the problems of accepting connections in high concurrency applications . One of the significant points in opting for asynchronous queue-digester-based solutions is, in my opinion, the management of the client-server relationship from the point of view of authentication, authorization , limitations, etc. This reflection did not take long to bring to my mind the hell of authorization flows in distributed systems and how complex (and absurd) they turn out to be. In this article we will try to summarize authorization flows , the complications we have in di

related reading