diff --git a/guide/index.html b/guide/index.html index e8af445..af9cbfc 100644 --- a/guide/index.html +++ b/guide/index.html @@ -69,19 +69,13 @@

Introduction

What's OpenIddict?

-

OpenIddict aims at providing a simple and easy-to-use solution to implement an OpenID Connect server in any ASP.NET Core 1.x or 2.x application.

-

OpenIddict is based on -AspNet.Security.OpenIdConnect.Server (codenamed ASOS) to control the OpenID Connect authentication flow and can be used with any membership stack, including ASP.NET Core Identity.

-

OpenIddict fully supports the code/implicit/hybrid flows and the client credentials/resource owner password grants. You can also create your own custom grant types.

-

Note: OpenIddict natively supports Entity Framework Core and Entity Framework 6 out-of-the-box, but you can also provide your own stores.

-

Note: the OpenIddict 2.x packages are only compatible with ASP.NET Core 2.x. -If your application targets ASP.NET Core 1.x, use the OpenIddict 1.x packages.

-
+

OpenIddict was born in late 2015 and was initially based on AspNet.Security.OpenIdConnect.Server +(codenamed ASOS), a low-level OpenID Connect server middleware forked from OWIN/Katana's OAuthAuthorizationServerMiddleware. In 2020, ASOS was merged into OpenIddict 3.0 +to form a unified stack under the OpenIddict umbrella, while still offering an easy-to-use approach for new users and a low-level experience for advanced users.

Why an OpenID Connect server?

Adding an OpenID Connect server to your application allows you to support token authentication. -It also allows you to manage all your users using local password or an external identity provider -(e.g. Facebook or Google) for all your applications in one central place, -with the power to control who can access your API and the information that is exposed to each client.

+It also allows you to manage all your users using local password or an external identity provider (e.g. Facebook or Google) for all your +applications in one central place, with the power to control who can access your API and the information that is exposed to each client.

diff --git a/manifest.json b/manifest.json index a605997..1644eb7 100644 --- a/manifest.json +++ b/manifest.json @@ -57,7 +57,7 @@ "output": { ".html": { "relative_path": "guide/index.html", - "hash": "DlLRNRY+B9DhbY4JF7UInQ==" + "hash": "NTmSbkoLbzVa/UZPkNhi1A==" } }, "is_incremental": false,