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.

Sign up for GitHub

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

Jump to bottom

enhance reliability #2

Open
Mannshoch opened this issue Dec 7, 2018 · 5 comments
Open

enhance reliability #2

Mannshoch opened this issue Dec 7, 2018 · 5 comments
Labels
0. Needs triage enhancement New feature or request

Comments

@Mannshoch
Copy link

Mannshoch commented Dec 7, 2018 •
edited
Loading

If "user_external" does not work, no user can currently log on.
Please add something like this.
If the user login is accepted by IMAP and if user not available create the user, otherwise replace the login credentials in the Nextcloud database with the password of the accepted login. Then add a "need IMAP Login" flag to the accounts created by Imap.

If a user login matches a login already available in the nextcloud database but Imap does not accept it, mark the user in the backend with a "Maybe a login problem" accept the login and tell this administrator. This allows the administrator to check whether an account is no longer available and should be removed from Nextcloud.
If the IMAP server is unavailable, but the login credentials are correct and no flag "Maybe a login problem" is available, allow the user to log in (and assume that there are only temporary connection problems). If "user_external" is disabled, all users remain in the Nextcloud database and can continue logging in.
@MariusBluem MariusBluem transferred this issue from nextcloud/apps Dec 20, 2018
@violoncelloCH
Copy link
Member

If I understand you correctly, this is a duplicate of #15
so can we close this in favour of #15?

@violoncelloCH violoncelloCH added the duplicate This issue or pull request already exists label Dec 21, 2018
@violoncelloCH violoncelloCH changed the title [user_external] enhance reliability enhance reliability Dec 21, 2018
@Mannshoch
Copy link
Author

I looked at #15 At moment I prefer my Issue, because its more detailed. So I would prefer to mark #15 as duplicate.
What's your rating for each of those two issues?

@violoncelloCH
Copy link
Member

violoncelloCH commented Dec 25, 2018 •
edited
Loading

I understand that you think this one is more detailed. It's more that this one (I'm sorry to say this) is more complicated to understand because of your language (the grammatical structure and wording).
If you could make your post easier to understand (it doesn't have to be perfect, I'm not a native speaker too), I'm happy to change this and chose your issue as the primary one. But the way it is at the moment I think this one is hard to understand (at least for me it is).

@Mannshoch
Copy link
Author

Thanks for the feedback.
I hope it's better this time.

@violoncelloCH
Copy link
Member

Thank you for updating your post! I think I get your point now.
So your feature request is addressing the same "issue" but with a different approach than #15. So I think we will keep them both open.
However your approach would be much more complex to implement I think.

@violoncelloCH violoncelloCH added enhancement New feature or request 0. Needs triage and removed duplicate This issue or pull request already exists labels Dec 30, 2018
@pelaxa pelaxa mentioned this issue Oct 7, 2019
Closed
@Mannshoch Mannshoch mentioned this issue Oct 23, 2019
Closed
@oriolo oriolo mentioned this issue Mar 8, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0. Needs triage enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mannshoch @violoncelloCH