Creating users for internal authentication
See original GitHub issueI would like to have an option to create users per demand to be moderators on the sessions via composer or some args.
I run jitsi on ECS and the only way to create users is to use a personalized Dockerfile and ADD
my USER.dat on the /config/data/meet%2ejitsi/accounts
path.
The documentation indicate that the only way to create users is running inside the container the prosodyctl
command, but should be a way to create users in the building process.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Creating a User Account (Internal Authentication)
Within the User Information tab, User details can be created, viewed and edited. User Roles, Process assignment and default logins can all be...
Read more >Configuring Users for Internal Database of an Instant AP
Click Users for Internal Server, to view the contents of the Users for Internal Server tab. Enter the user name in the Username...
Read more >Add a User with Options to the Internal Database - 629411
In the Security Console, click Identity > Users > Add New With Options. Decide which options that you want to assign to the...
Read more >Creating an Internal User - TechDocs - Broadcom Inc.
Click Create Internal User on the Home Page. · Click [. Tasks. ] > Users and Authentication > Create Internal User. from the...
Read more >Tutorial: Configure a domain with the internal user database ...
Choose Security, Internal users, Create internal user. Name the user new-user and specify a password. Then choose Create. Choose Roles, Create role.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This could be implemented by using a file which can be mounted into the container. It could be in this format:
username\tpassword\n
So each line would contain username and password separated by a TAB. This is easy to parse in bash and create the users on container startup if the file exists.
I don’t think that can work because we need to know the exact env variables in order to pass them around.