Identity and access management

Video 1:  video1

SAML: video2

Oauth2 and OIDC: video3


single sign on: 
part1 part2


Ultimate Guide of Identity and access management: here


OIDC or SAML, which is preferred  choice for single sign on?

Both OpenID Connect (OIDC) and Security Assertion Markup Language (SAML) are widely used protocols for Single Sign-On (SSO) in modern web applications. However, the best protocol for SSO depends on the specific needs and requirements of the application and the organization using it.

OIDC is a modern, lightweight and flexible protocol that is designed to work well with modern web and mobile applications. It is built on top of OAuth 2.0, which makes it easier to integrate with APIs and microservices. It supports modern features such as JSON Web Tokens (JWT) and allows for more fine-grained control over access and authorization.

SAML, on the other hand, is an older and more established protocol that has been around for a longer time. It is widely used in enterprise environments and is well-suited for integrating with legacy systems. It provides strong security features such as message signing and encryption and allows for more control over user authentication.

In general, if you are building a new web or mobile application, and you have the flexibility to choose the protocol, OIDC may be a better choice due to its modern features and flexibility. However, if you are working in an enterprise environment and need to integrate with legacy systems, or if you need stronger security features such as message signing and encryption, SAML may be a better choice.


Comments

Post a Comment

Popular posts from this blog

Docker Imp points

  1. docker run -it <image> <any command like ls>  - It will start the container execute the command and stop the container.The status of the stopped container can be seen using docker ps -a 2. docker run -it --rm <image> <any command like ls> - It will do the same the same hing, but after stopping it will also kills the container 3. If we run an docker image without specifying -d(detached mode),then we will enter into container directly and if we exit the container will be stopped 4.If we run container in detached mode by specifying -d,as shown below image will run in background,we can connect to it using exec. Eg:$docker run -itd <image> 5. About user in docker file: - If we specify any user in dockerfile, all the commands will be executed by that user and in  the image that user is retained, i.e if you make a container out of it,we will get same user. - If we want to switch user,you can do so using another user instruction in docker file a...
Read more

Docker volumes backup and restore & Docker networks

 Backup and restore docker volumes Official link Youtube Best aricle for volumes backup and restoration Docker neworks: Network drivers: Network driver summary : Bridge network Official link : The default network used by docker if we do not specify any option is bridge network We can create our own bridge network, Containers on the default bridge network can only access each other by IP addresses, unless you use the --link option , which is considered legacy. On a user-defined bridge network, containers can resolve each other by name or alias. We can create bridge network as shown below      $docker network create <network name>   If we don't specify any network driver then by default it is bridge and we can define subnet and default gateways by using different flagsf we can add container to user defined network 2 ways While creating docker container from image using --network or --net flag        $docker run --it --net=<network na...
Read more