Openiddict openiddictRequest object in login controller returns null

Confirm you’ve already contributed to this project or that you sponsor it

• I confirm I’m a sponsor or a contributor

Version

3.x

Describe the bug

Hi In authorization flow, when control reach to authorization controller, am able to access openiddictRequest Object successfully using below code var request = HttpContext.GetOpenIddictServerRequest() . (Ref Image 01_authorize_method_Openiddict_is_proper.png). However post challenge method in Authorize method, the control goes to accountcontroller (account/login) method . In that controller, the openiddict request object is always coming as null using HttpContext.GetOpenIddictServerRequest() . (Ref 02_account_login_openiddict_request_null.png). This behaviour does not allow me to proceed and check which client id is requested and based on that we could render view. Could you please guide with regard to this issue Below is challenge code in authorize method /connect/authorize")]

return Challenge( authenticationSchemes: CookieAuthenticationDefaults.AuthenticationScheme, properties: new AuthenticationProperties { RedirectUri = Request.PathBase + Request.Path + QueryString.Create( Request.HasFormContentType ? Request.Form.ToList() : Request.Query.ToList()) });

The authentication configuration services.AddAuthentication(option => { // Default authentication scheme is cookie, to allow users redirect to login page option.DefaultAuthenticateScheme = CookieAuthenticationDefaults.AuthenticationScheme;

                    option.DefaultChallengeScheme = JwtBearerDefaults.AuthenticationScheme;
                }).AddCookie(CookieAuthenticationDefaults.AuthenticationScheme, options =>
                {
                    //** added loginpath for openiddict 
                    options.LoginPath = "/Account/Login";

openiddict configuration.txt

To reproduce

Exceptions (if any)

-

[salimz1]

Thanks Kevin for the quick support. It is helpful. I can try the suggested options to render view.

[kevinchalet]

Thanks!

The behavior you’re seeing is not a bug and is completely expected: your login endpoint is not an endpoint managed by OpenIddict so HttpContext.GetOpenIddictServerRequest() will always return null.

To achieve what you want, you must manually flow the parameters you need between the authorization endpoint (your /connect/authorize action) and your login endpoint. For that, you can attach a custom parameter when triggering the challenge in your authorization endpoint action and use a custom event handler to add it to the login endpoint path:

[HttpGet("~/connect/authorize")]
[HttpPost("~/connect/authorize")]
[IgnoreAntiforgeryToken]
public async Task<IActionResult> Authorize()
{
    var request = HttpContext.GetOpenIddictServerRequest() ??
        throw new InvalidOperationException("The OpenID Connect request cannot be retrieved.");

    // ...

    return Challenge(
        authenticationSchemes: IdentityConstants.ApplicationScheme,
        properties: new AuthenticationProperties
        {
            Parameters =
            {
                ["client_id"] = request.ClientId
            }
        });
    
    // ...
}

services.AddAuthentication()
    .AddCookie(options =>
    {
        // ...

        options.Events.OnRedirectToLogin = context =>
        {
            var id = context.Properties.GetParameter<string>("client_id");
            if (!string.IsNullOrEmpty(id))
            {
                context.RedirectUri = QueryHelpers.AddQueryString(context.RedirectUri, "client_id", id);
            }

            context.Response.Redirect(context.RedirectUri);

            return Task.CompletedTask;
        };
    });

Hope it’ll help.