Creation of users/application that are not localhost

[Gupta-Krishnaa]

In the Elsa Documentation for 3.0, in order to create a new user we are supposed to call the following rest endpoint

https://server-name/elsa/api/identity/applications \
--header 'Content-Type: application/json' \
--data '{
    "name": "Postman",
    "roles": ["admin"]
}

However, it's applicable only for localhost as the documentation states

By default, creating applications is allowed for anonymous requests from the localhost.

I would like to host the application on my personal azure platform with App Service which will not have localhost. What should be done in that case ?

cc: @sfmskywalker @agriffard @VahidNaderi @mohdali

[Gupta-Krishnaa]

Any updates ?

cc: @sfmskywalker @agriffard @VahidNaderi @mohdali

[mohdali]

I'm not exactly sure but can't you do something from the KUDU console using PowerShell?

[Gupta-Krishnaa]

Can you elaborate on this ? Do you mean to say that I should fire a rest call from KUDU powershell which creates a user/application ?

For example:

https://server-name/elsa/api/identity/applications

[mohdali]

I haven't tried myself but I assume it should work if it acts as a local shell. You can fire a web request from there to see if it creates the desired user.

[Gupta-Krishnaa]

I tried as you suggested but I am getting Forbidden 403:

Here s the detail:

And Lastly,

The result:

Any ideas ?

[sfmskywalker]

In an ideal scenario, Elsa Studio would guide users through a setup procedure during its initial launch. This would facilitate the creation of an admin user tailored to the target environment, ensuring a seamless experience.

Currently, Elsa Studio does not possess this feature. As a workaround, I recommend creating the user in a local environment. Once the user is successfully created, you can then migrate the database or the specific database records to your production environment. This method ensures that you have the necessary user configurations in place before deploying to a non-localhost environment like Azure App Service.

It's essential to ensure the security and integrity of your data during this process. Always backup your production database before making any changes and test the migration in a staging environment if possible.