IdentityServer4 icon indicating copy to clipboard operation
IdentityServer4 copied to clipboard

OpenID Connect and OAuth 2.0 Framework for ASP.NET Core

Results 47 IdentityServer4 issues
Sort by recently updated
recently updated
newest added

We are using Identity Server4 has two external login schemes(Azure Ad B2C and Azure AD). App1 -- has access to login with B2C App2 -- has access to login with...

question
wontfix

I have a requirment in which I have to sign out some user to which a jwt was emitted, but without the user having to know about this (so somehow...

question

I have some additional behavior, so I need to call protected api inside is4 when I try to authenticate with interactive user. So I'm using IdentityServerTools to issue access tooken...

question

### Issue / Steps to reproduce the problem This works: ``` services.AddDefaultIdentity(options =>{ options.User.RequireUniqueEmail = true; options.Stores.MaxLengthForKeys = 128; }) .AddRoles() .AddEntityFrameworkStores() .AddSignInManager() .AddDefaultTokenProviders(); ``` This throws a nullreference exception...

bug report

Try to create JwtToken with `Claim(type: "json", value: Dictionary{["foo"] = 1})` with at least one scope. The result is JWT with claim without original meaning. The real cause of this...

bug report

**"idp claim is missing" error received when trying to login after leaving the browser idle for sometime.** I use IS4 as SSO for my MVC as well as React Webapp....

bug report

The behaviour of the `scope` parameter is different between the different types of flow: - In the Auth Code flow, if the `scope` parameter is missing or empty, I get...

bug report

**Please find below the steps I applied in order to generate Reference Token instead of JWT:** 1. In the [Clients] table, I updated property [AccessTokenType] = 1. Please note that...

bug report

As reported #1501, the issuer URI is converted to lowercase by IdentityServer in its `.well-known/openid-configuration` response. This is invalid behavior, because the *path* part of the URL is case sensitive...

bug report

### Issue / Steps to reproduce the problem Setup a basic mTSL client with **AccessTokenType.Reference**. Grab a new token and run an introspection on that token: `{ "iss": "https://localhost:5000", "nbf":...

bug report