Claims & Scopes
Learn how claims and scopes can be used for standards-based authorization.
Articles
Implementing Claims Best Practices
Using the Curity Identity Server to issue custom claims
Claims Best Practices
Recommendations on using claims in real world systems
Scope Best Practices
Recommendations on designing scopes in real world systems
Consent and Claims
The relationship between Consent and Claims.
Default Scopes
How to use the default scope with a set of default claims.
The Claims Authority
What is a Claims Authority.
Introduction to Scopes
Scopes and their relation to claims.
Claims Explained
This article provides a comprehensive overview of the claims ontology. Scopes, claims, tokens and how they are related.
Using Claims in APIs
How to create a claims-based architecture for APIs and microservices.
Centralizing Identity Data
How the claims infrastructure can be used to centralize the identity data.
Scopes, Claims and the Client
Thinking about claims from a client perspective.
Introduction to Claims
What are Claims and how are they used.
Scopes vs Claims
A short explanation of the differences between scopes and claims.
Videos
A claim is statement that a particular entity has a particular property. In authentication, we usually think of claims as assertions about a user, as asserted by the Identity Provider. Claims are critical to reach the highest level in the API Security Maturity model. When designing a token-based architecture, it's important to understand how identity data is passed around. Claims provide a fundamental means for how to trust that the data is valid and true. A scope is a grouping of claims. In OAuth, a scope is defined as a string that may represent a resource the Client requests access to. The Scope is what gives access to APIs (with a valid token). But Scopes are also what gives access to claims.