locked
Blazor WASM (hosted) - configure identity server options RRS feed

  • Question

  • User379720387 posted

    Halfway through a lengthy writeup from MSFT about Identity Server (IS) and hosted Blazor WASM apps.

    At this point I need your guidance as the writer's choice of words has become imprecise. There is a clue maybe in the bolding of one in "use one of the following approaches"?  Approaches are: API Authorization options and Profile Service

    Options in my mind optional and why would they pertain only to API Authorization and not the rest of the WASM app?

    Is this really a one or the other case?

    Are both options equal?

    Which one is easier to read and maintain down the road?

    Will either option preclude me from adding a Blazor Server app to this solution that utilizes  the Controllers from the WASM.Server project?

    Saturday, May 15, 2021 1:35 PM

Answers

  • User475983607 posted

    IdnetityServer4 returns a standard (default) set of claims.  IProfileService is an extension point that lets you write code to add whatever claim(s) you like to the access token.   The authorization options is another way to do the same.  I use the IProfileService approach.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, May 15, 2021 5:29 PM