[Blazor][Wasm]: add support for customizing the logout process by allowing us to pass additional hints (throught qs parameters)

[luisabreu]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Currently, and unlike what happens during the login process, it seems like there's no way to customize the logout URL that is generated during the logout process (Azure AD).

Expected Behavior

The login/logout API should be symmetric. In other words, if I can use InteractiveRequestOptions to customize the login experience of the user, then I should be able to do the same thing during the logout process (ex.: I can use the loginHint during the login process, but can't set the logoutHint when the user signs out).

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

8.0.101

Anything else?

No response

[KiristonK]

Hello, for anyone, looking for workaround, here's a solution that worked for me like a charm with logout_hint for promptless logout:

var logoutOptions = new InteractiveRequestOptions
     {
         Interaction = InteractionType.SignOut,

         ReturnUrl = null!
     };
 logoutOptions.TryAddAdditionalParameter("logoutHint", authUser.User.FindFirst("login_hint")?.Value);
 NM.NavigateTo($"./authentication/{RemoteAuthenticationActions.LogOut}", new NavigationOptions
 {
     HistoryEntryState = logoutOptions.ToState()
 });

Where NM is an NavigationManager instance, and .ToState() extension looks like this:

public static class InteractiveRequestOptionsExtenstions
{
    private static JsonSerializerOptions _InteractiveRequestOptions;
    private static JsonSerializerOptions InteractiveRequestOptions => _InteractiveRequestOptions ??= new JsonSerializerOptions
    {
        PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
        WriteIndented = false
    };

    public static string ToState(this InteractiveRequestOptions options)
    {
        return JsonSerializer.Serialize(options, InteractiveRequestOptions);
    }

    public static InteractiveRequestOptions FromState(this string state)
    {
        return JsonSerializer.Deserialize<InteractiveRequestOptions>(state, InteractiveRequestOptions);
    }

}

P.S.
If anyone has better solution, will be glad to improve my answer!

[alfred-zaki]

@KiristonK thanks! i was doing something similar but my mistake was setting parameter key to "logout_hint" not "logoutHint"
Thank you so much for your help, hopefully MS do the right thing and get this to the library to be done same as NavigateToLogin