OpenId Connect provision within existing websites

[DanielNewmanUK]

Which version of Duende IdentityServer are you using? IdentityServer3

Which version of .NET are you using? .Net Framework 4.8

Describe the bug

This is a question rather than a bug.

We wish to utilise IdentityServer so that it will allow our applications to act as an OpenID Connect provider. We see lots of examples to do this using ASP.Net Identity or Entity Framework but in our case, we are using system.web.security.membership or a custom authentication scheme.

How can we configure IdentityServer to use our existing authentication approaches? I saw a reference to adding custom stores, but there weren't any examples as to how to do this.

Thank you

Expected behavior

We are wanting our users to login to our applications using their existing methods. We then want to redirect our users to another application, which will authenticate this user based on the first application's logged in user.

Log output/exception with stacktrace

data

Additional context

Add any other context about the problem here.

[RolandGuijt]

I'm sorry but IdentityServer3 has been out of support for a while now. But having said that: Microsoft's membership has a lot of shortcomings that doesn't make it suitable for an identity provider. But there is an example with MembershipReboot that tried to overcome these problems.

[DanielNewmanUK]

Thank you @RolandGuijt. Our platforms already have upgrade pathways to .Net Core, so we can look into incorporating IdentityServer4 into those upgraded solutions. Thank you for your response.

[AndersAbel]

@DanielNewmanUK Just for the record, IdentityServer4 is also out of support. The only supported versions are Duende.IdentityServer 6.x and 7.x.