Anish's Notebook

1. Authorization flow with PKCE https://github.com/Anish407/OpenID-Connect---Authorization-flow-with-PKCE When a browser is involved in the communication, it is not safe to store the id and access tokens in the it. Browser is not considered to be safe. Everything you send to the browser is readable and can be extracted, manipulated, and potentially exploited. That's why authorization code flow was invented.   Using that flow, tokens aren't sent in the redirect back to the client from the authorization endpoint. Instead, a code is sent. The code can then be used by the client to do a back channel request. That's a request done at the client level the browser doesn't know about. In this request, the code is exchanged for an access token at a token endpoint. When the client does the request to the token endpoint, it has to present its client ID and secret. If the OpenID scope is among the requested scopes, the token endpoint also sends the identity token ...

Service bus is a refined version of the queue service. We can create topics for PUB/SUB.  Firstly we need to create a namespace, under this namespace we can create queues or topics. The Service bus explorer can be used to send/receive/peek message on the service bus. If we read the message then the message is removed from the queue, whereas with peek we can see the message without removing it. To get to the service bus explorer , create a queue in the service bus namespace An enterprise service bus implements a communication system between mutually interacting software applications in a service-oriented architecture. QUEUE PROPERTIES TIME to Live We can set a common time to live or each message in the queue, this can be done by configuring the TTL at the queue level. Each message can have its own TTL which will override the Queue TTL. LOCK Duration: When we set the lock duration on a message what happens is that once a receiver receives the messages no other receivers or subscribe...