Workshop: Creating an OpenIdConnect Identity Provider with IdentityServer with Roland Guijt

Kurskod DSWS-IdentityServer

Workshop: Creating an OpenIdConnect Identity Provider with IdentityServer with Roland Guijt

In connection with our developer conference DevSum, we offer a select few workshops with internationally known experts.

Using an OpenIdConnect Identity Provider has become the standard for authentication in many organizations. The cloud offers you many ready-to-go options but often these are not flexible enough.
The open source IdentityServer lets you build your own and is designed with flexibility in mind. In this workshop we'll go through all the details. 

Pris
7450 kr (exklusive moms)
Kursform
På plats

Leveransformer kan variera beroende på ort och datum.

På plats innebär att kursen hålls i klassrum. Läs mer här.
LiveClass innebär att kursen hålls som en lärarledd interaktiv onlineutbildning. Läs mer här.

Längd
1 dag
Ort och datum
24 maj
Stockholm

Boka utbildning

We'll go way beyond the "hello world" demo: At the end of the day you'll know how to create a usable identity provider suitable for production and you'll have a good idea of both the basic and more advanced features of IdentityServer.


About Roland Guijt

Roland is a Microsoft MVP, ASP.NET Insider and Pluralsight author enjoying a constant curiosity around new techniques in software development. His focus is on all things .NET and browser technologies.
As a long-time trainer and speaker, he led many courses on these topics and spoke about these topics at many international conferences

Content details


  •  What is an identity provider?
  • OpenIdConnect terminology (users, resources, clients)
  • Show a simplified token service with in-memory data
  • Show how to consume it with clients and apis
  • Add database support (built-in EF contexts)
  • Creating a custom user datastore
  • How to add support for users
  • Using Identity as a user store
  • Adding claims with a profile service
  • Grants and flows
  • Using refresh tokens
  • Using reference tokens
  • Adding support for external identity providers (google, facebook, ad)
  • Using the id token for all kinds of authorization data is not a good idea
  • Creating an authorization service to cope with this

Få inspiration & nyheter från oss

Jag godkänner att Cornerstone skickar mig nyheter via e-post