How Does Claim Based Authentication Works?

This is the simplified version of how claims work. The easiest way to think about how claims work is to take a real world example. Let’s imagine that you need to board an aero plane. First you need to check in. That could be at the ticket counter or that could be online. Both require you to authenticate yourself in different ways. The ticket counter requires you to show some form of ID and that ID comes from a trusted source. Online you are forced to login and that login must be trusted in order for you to print your boarding pass
Your Boarding pass contains a lot of extra information rather than just your name. It contains your destination, the gate you are leaving from, your flight number, and also your seat information. When you reach the gate, the gate agent checks your boarding pass. This agent doesn’t really care whether your claim came from the ticketing agent or from your printer at home. The boarding pass is trusted claim and you are allowed to get on your flight. If we translate this to software, that boarding pass is a signed security token from a trusted issuer. Your application would validate it and allow the user or application presenting that token to have access to the resource that was requested.