Feature: Embedding inside current Blazor-Server application

[itniels]

It would be super cool to be able to embed this inside an existing Blazor-Server application under say /elsa or some configurable URL, so that it is more of a component than a whole application.

We are already developing a dashboard, and want to integrate Elsa into it, we could of course run a separate instance and just iframe it in, but being able to just reuse all the login logic etc we already have, it would make sense to simply embedding it in a page instead, would this be a possible feature?

[hpposch]

I also have the same "problem" I can run my instance of elsa under https://localhost:6001, but i want it to run by default under https://localhost:6001/wf So in addition to that login should be accessed via https://localhost:6001/wf/login - and so on.. Under https://localhost:6001 i want to acces my custom main page.

How can i do that? I already tried to change the basepaths but it did not work for me...

[itniels]

@hpposch The elsa studio consists of a few blazor components, and while undocumented or tested, it should be possible to use those components in your own blazor-server application, there is some routing stuff that needs handled for it to work.

This is something that is on the roadmap to get working and properly documented as far as I am aware. And I have not tried to to do so yet.

Hope this helps

[hpposch]

Hi @itniels thank you for your response. I understand that elsa is still under development and therefore some parts are not documented. Anyway i would need a quick solution to overcome the login dialog. Is there a simple way to disable the login dialog or is there anything like https://admin:password@localhost:5001 At the moment this is the last step that holds me back from using elsa in a real production environment

[ILAOHE]

Have you solved this problem?

[cr0fters]

@hpposch did you ever get a solution for this? Sounds like I'm in a similar position to where you got to