Login with nested base path

[rolandgriesser]

Hi,

I think I've encountered this issue before already: When redirecting to the login page, the current implementation uses /login, which is an issue if Elsa Studio isn't hosted at the root level - e.g. I host Elsa Studio at /studio, thus the redirect url should be /studio/login.
If you look at the commit c6d60ba,
you can see that you had relative path's before.
Is this something I should fix on my side or is this a regression?

All the best, Roland

[sfmskywalker]

Hi @rolandgriesser , I don't see any behavior changes in that commit, just some code simplification.

• launchSettings.json: irrelevant
• ElsaIdentityAuthorizationService.cs‎: reformatting code
• ActivityWrapperBase: injecting a reusble serializer options.

However, I asked DeepWiki about options, and it reminded me that the Blazor WASM host is a good example of how to implement root paths. In this reference app, it is used for dynamic root paths to determine the current tenant ID (where the tenant ID is part of the root path), but the same principle applies to using a custom root path. Probably simpler, given that your root path is presumably static.