Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI: Admin user should not be listed before being actually created #1448

Closed
oupala opened this issue Mar 3, 2017 · 7 comments
Closed

CLI: Admin user should not be listed before being actually created #1448

oupala opened this issue Mar 3, 2017 · 7 comments
Assignees
Milestone

Comments

@oupala
Copy link
Contributor

oupala commented Mar 3, 2017

When installing FreshRSS via cli, the install process creates a user whereas it should not create a user.

>sudo -u www-data ./cli/do-install.php --default_user myuser --api_enabled --db-type sqlite
FreshRSS install…
• Remember to create the default user: myuser
	./cli/create-user.php --user myuser --password 'password' --more-options
• Remember to re-apply the appropriate access rights, such as:
	sudo chown -R :www-data . && sudo chmod -R g+r . && sudo chmod -R g+w ./data/
Result: success
>sudo -u www-data ./cli/list-users.php 
myuser
>sudo -u www-data ./cli/user-info.php -h --user myuser
FreshRSS error: user not found: myuser

The user is listed but does not exist. This is a bit inconsistent.

Why not set the default user not at install time, but at user creation time ?

This make it difficult to know whether I have to really create the user or not...

@Alkarex
Copy link
Member

Alkarex commented Mar 3, 2017

Related to #1445 #1447

@Alkarex Alkarex changed the title installing FreshRSS via cli should not create a user CLI: Admin user should not be listed before being actually created Mar 3, 2017
Alkarex added a commit to Alkarex/FreshRSS that referenced this issue Mar 3, 2017
@Alkarex
Copy link
Member

Alkarex commented Mar 3, 2017

Should be fixed in Alkarex@ae1bf1f / #1447

@Alkarex Alkarex closed this as completed Mar 4, 2017
@Alkarex Alkarex self-assigned this Mar 4, 2017
@oupala
Copy link
Contributor Author

oupala commented Mar 4, 2017

This bug is fixed.

But is it necessary to set the default user at install time?

Could it be possible that the default user is set at user creation time? The first created user would simply be the default one. In my opinion, this appears to be simpler. Don't you think?

@Alkarex
Copy link
Member

Alkarex commented Mar 4, 2017

This could be an option indeed. The historical reason is that there is a global configuration (including the name of the default user) and then user-specific configurations. Furthermore, it is more consistent with the possibility to reconfigure the default user to another user.

@oupala
Copy link
Contributor Author

oupala commented Mar 5, 2017

Historical reasons are usually bad reasons... ;-)

From a user point of view, what does it change for a user to be default one or not? Is he sort of an admin?

@Alkarex
Copy link
Member

Alkarex commented Mar 5, 2017

Historical was maybe a bad word: the situation is still the same. Yes, the default / admin user has additional rights (such as to create other users, change login type, etc.) and is also used for the content of the anonymous view.

@oupala
Copy link
Contributor Author

oupala commented Mar 15, 2017

I still think that admin user should be the first created user and hence should not be specified at install time. It would be more consistent.

An instance of FreshRSS without user cannot have a default admin user...

javerous pushed a commit to javerous/FreshRSS that referenced this issue Jan 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants