CODEWITHSUNDEEP
asp.net-identityopenididentityserver4openid-connect
Vivendi
Vivendi

Reputation: 20987

Invalid_client using OpenIdConnect in client application

I have an IdentityServer4 application running with ASP.NET Identity. I want to use that so users from another application can login through my remote identity server.

I have configured a client application in identity server with the following settings (showing only relevant settings):

ClientId: mvc
ProtocolType: oidc
ClientSecret: K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

(URLs to client app)
RedirectUri: https://localhost:44313/signin-oidc
PostLogoutRedirectUri: https://localhost:44313/signout-callback-oidc

GrantType: Hybrid

client id

enter image description here

My client application (server side Blazor app) has the following settings configured in Startup.cs.

        // Add authentication
        services.AddAuthentication(options =>
        {
            options.DefaultScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            options.DefaultChallengeScheme = OpenIdConnectDefaults.AuthenticationScheme;
        })
        .AddCookie(CookieAuthenticationDefaults.AuthenticationScheme)
        .AddOpenIdConnect(OpenIdConnectDefaults.AuthenticationScheme, options =>
        {
            options.RequireHttpsMetadata = false;
            options.SignInScheme = CookieAuthenticationDefaults.AuthenticationScheme;
            options.Authority = "http://localhost:5000/"; // local identity server url
            options.ClientId = "mvc";
            options.ClientSecret = "K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=";
            options.ResponseType = OpenIdConnectResponseType.CodeIdToken;
            options.SaveTokens = true;
            options.GetClaimsFromUserInfoEndpoint = true;
            options.Scope.Add("profile openid web_api");
        });

When I start my client app, I then get redirect to my IdentityServer login page. I can then login with a username and password. When I login I then get redirected back to my client application https://localhost:44313/signin-oidc.

But then I get the following error on that page:

OpenIdConnectProtocolException: Message contains error: 'invalid_client', error_description: 'error_description is null', error_uri: 'error_uri is null'.

To me it looks like I am using the correct ClientId?

What am I doing wrong?

Upvotes: 14

Views: 21137

Answers (3)

Mayur Dighe
Mayur Dighe

Reputation: 419

I recently faced this issue and discovered that my application was making a POST request to the OIDC Provider on the Token endpoint. While the OIDC Provider was set to accept Basic Authentication.

Once that was resolved, my issue was resolved.

Upvotes: 0

Kunal Khatri
Kunal Khatri

Reputation: 471

Please check Client Configuration (clientId), If it matches given client configuration or not.

In my case, issue was related with secret.

2 Things to note for secret issue:

  1. In the client application ,'ClientSecret' should be the 'unencryptedvalue' - plaintext.('secret' in following example)
  2. While doing the configuration for all clients, in identity server, please check the secret.Type, it should be 'SharedSecret'.

Example:

Secret secret = new Secret("secret".Sha256(), "Description");
secret.Type = "SharedSecret";

Upvotes: 2

user4864425
user4864425

Reputation:

ClientSecret should contain the unencrypted value. Take a look at the documentation.

In your case secret.

options.ClientSecret = "secret";

I didn't look further, so if this change doesn't solve it then please let me know.

Upvotes: 12

Related Questions