locked
What is relation between identity and cliam authentication RRS feed

  • Question

  • User264732274 posted

    anyone can explain  what is relation between identity and claim authentication with example.

    i found below one

    •  Claims Based
      •  ASP.NET Identity supports claims-based authentication, where the user’s identity is represented as a set of claims. Claims allow developers to be a lot more expressive in describing a user’s identity than roles allow. Whereas role membership is just a boolean (member or non-member), a claim can include rich information about the user’s identity and membership.

    what is claim ?

    is it any kind of authentication system ?

    i guess claim is token based auth......am i right ?

    give me a scenario that when identity use claim auth. thanks

    Monday, March 14, 2016 1:36 PM

Answers

  • User-1068454292 posted

    Hi sudip_inn,

    sudip_inn

    what is claim ?

    The ASP.NET Identity is a framework which supports both the Form authentication and claims-based authentication. For more detail, please see the following links:

    http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity

    An Introduction to Claims

    sudip_inn

    is it any kind of authentication system ?

    i guess claim is token based auth......am i right ?

    Think of a claim as a piece of identity information such as name, e-mail address, age, membership in the Sales role. The more claims your application receives, the more you’ll know about your user. You may be wondering why these are called “claims,” rather than “attributes,” as is commonly used in describing enterprise directories. The reason has to do with the delivery method. In this model, your application doesn’t look up user attributes in a directory. Instead, the user delivers claims to your application, and your application examines them. Each claim is made by an issuer, and you trust the claim only as much as you trust the issuer. For example, you trust a claim made by your company’s domain controller more than you trust a claim made by the user herself. WIF represents claims with a Claim type, which has an Issuer property that allows you to find out who issued the claim.

    Please see An Introduction to Claims

    suggest you could make an example with it, you can refer to the following links:

    The Claims-Based Identity Model

    Managing Claims and Authorization with the Identity Model

    Claims Based Authorization

    Claims Aware Forms Authentication

    Best regards

    Pan

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 15, 2016 8:31 AM
  • User1779161005 posted

    There is no such thing as "claims based authentication". That's like saying "role based authentication" -- it just doesn't make sense.

    The proper term is "claims based identity", which means you use claims to model the identity of your users. Claims are flexible ways of modeling the user's identity and a role is just a claim. So is email, name, age, etc...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 15, 2016 2:24 PM

All replies

  • User-1068454292 posted

    Hi sudip_inn,

    sudip_inn

    what is claim ?

    The ASP.NET Identity is a framework which supports both the Form authentication and claims-based authentication. For more detail, please see the following links:

    http://www.asp.net/identity/overview/getting-started/introduction-to-aspnet-identity

    An Introduction to Claims

    sudip_inn

    is it any kind of authentication system ?

    i guess claim is token based auth......am i right ?

    Think of a claim as a piece of identity information such as name, e-mail address, age, membership in the Sales role. The more claims your application receives, the more you’ll know about your user. You may be wondering why these are called “claims,” rather than “attributes,” as is commonly used in describing enterprise directories. The reason has to do with the delivery method. In this model, your application doesn’t look up user attributes in a directory. Instead, the user delivers claims to your application, and your application examines them. Each claim is made by an issuer, and you trust the claim only as much as you trust the issuer. For example, you trust a claim made by your company’s domain controller more than you trust a claim made by the user herself. WIF represents claims with a Claim type, which has an Issuer property that allows you to find out who issued the claim.

    Please see An Introduction to Claims

    suggest you could make an example with it, you can refer to the following links:

    The Claims-Based Identity Model

    Managing Claims and Authorization with the Identity Model

    Claims Based Authorization

    Claims Aware Forms Authentication

    Best regards

    Pan

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 15, 2016 8:31 AM
  • User1779161005 posted

    There is no such thing as "claims based authentication". That's like saying "role based authentication" -- it just doesn't make sense.

    The proper term is "claims based identity", which means you use claims to model the identity of your users. Claims are flexible ways of modeling the user's identity and a role is just a claim. So is email, name, age, etc...

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, March 15, 2016 2:24 PM