This package will enable your ASP.NET application to work with Okta via OAuth 2.0/OIDC. You can follow our instructions below, check out our examples on GitHub or jump to our guides to see how to configure Okta with your ASP.NET applications.
We also publish these other libraries for .NET:
This library uses semantic versioning and follows Okta's library version policy.
✔️ The current stable major version series is: 1.x
| Package | Version | Status | Compatibility | Branch |
|---|---|---|---|---|
Okta.AspNet.Abstractions |
3.x | ✔️ Stable | .NET Standard 2.0 and .NET Framework 4.5.2 or higher. | master |
Okta.AspNet |
1.x | ✔️ Stable | .NET Framework 4.5.2 | master |
Okta.AspNetCore |
1.x | .NET Standard 2.0 and .NET Core 2.x | okta-aspnetcore-2.x | |
Okta.AspNetCore |
3.x | ✔️ Stable | .NET Core 3.x and .NET 5.0 | master |
The latest release can always be found on the releases page.
If you run into problems using the SDK, you can
- Ask questions on the Okta Developer Forums or email [email protected].
- Post issues here on GitHub (for code errors)
An Okta account (sign up for a forever-free developer account)
If you want to build an ASP.NET MVC application we highly recommend you to check out this guide to see what you need to get started and how sign users in your web application using the Okta ASP.NET SDK. You can also check out the following resources:
Also, if you want to build an ASP.NET Web API application check out this guide to see how to protect your endpoints using the Okta ASP.NET SDK. You can also check out the following resources:
- Getting started with ASP.NET Web API
- Getting started with ASP.NET Core Web API
- Refreshing Access Token in ASP.NET MVC or WebForms App
To learn more about this library you can explore the following additional resources:
Issues and Pull Requests are welcome! To build the project, clone and build it with Visual Studio 2017 or newer.
Be aware that these assemblies are strong-named:
- Okta.AspNet
- Okta.AspNet.Abstractions
- Okta.AspNet.Test
In order to be able to debug those assemblies locally you can either remove strong-naming by unchecking "Sign the assembly" check box in the project options or temporarily add them to ignore list using the Strong Name Tool:
sn.exe -Vr (path-to)\Okta.AspNet.dll
sn.exe -Vr (path-to)\Okta.AspNet.Abstractions.dll
sn.exe -Vr (path-to)\Okta.AspNet.Test.dll
Check out the Contributing Guide.