You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the most recent version of Nextcloud Snap on Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-130-generic x86_64)
When I try to integrate my iPhone's calendar and contacts by using the Nextcloud App's configuration profile, I will be presented with the option to enter a password. No matter if I
enter mine
leave it blanc
generate an App password, which I then enter there
I will be presented with a "DAAccountValidationDomain-Fehler 100.", which I assume translates to "DAAccountValidationDomain-Error 100.".
This issue first appeared after I enabled TOTP 2FA for my account. I already tried disabling 2FA for my account in the meantime but no luck. The error is still there.
Steps to reproduce
Install Nextcloud
Install TOTP App
Enable TOTP for your user
Use iOS Nextcloud App to get a configuration profile
Try to enable the profile <- this is where the error occurs
Disable TOTP for your user (the app is still active because I need the Admin account which doesn't need to be integrated anywhere is under maximum security)
Load new config profile
Try to enable it <- the same error still occurs
Expected behavior
I think it's fair to fail when TOTP is enabled since there is no way to enter the code but it should work with an App password, which it doesn't.
In a perfect world I'd expect the Nextcloud App, which is already authenticated as your user, to generate and include an app password in the configuration profile. I don't know about the limitations from Apple's side in this regard though.
More than anything I'd expect for the authentication to work at all ^^
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
I left some fiels as none in the info about my setup because I've had this issue since multiple major version upgrades and my current version is not going to affect the outcome. I'm using the Snap so I'm usually auto-updated to the latest available.
The text was updated successfully, but these errors were encountered:
Bug description
I am using the most recent version of Nextcloud Snap on Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-130-generic x86_64)
When I try to integrate my iPhone's calendar and contacts by using the Nextcloud App's configuration profile, I will be presented with the option to enter a password. No matter if I
I will be presented with a "DAAccountValidationDomain-Fehler 100.", which I assume translates to "DAAccountValidationDomain-Error 100.".
This issue first appeared after I enabled TOTP 2FA for my account. I already tried disabling 2FA for my account in the meantime but no luck. The error is still there.
Steps to reproduce
Expected behavior
I think it's fair to fail when TOTP is enabled since there is no way to enter the code but it should work with an App password, which it doesn't.
In a perfect world I'd expect the Nextcloud App, which is already authenticated as your user, to generate and include an app password in the configuration profile. I don't know about the limitations from Apple's side in this regard though.
More than anything I'd expect for the authentication to work at all ^^
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
I left some fiels as none in the info about my setup because I've had this issue since multiple major version upgrades and my current version is not going to affect the outcome. I'm using the Snap so I'm usually auto-updated to the latest available.
The text was updated successfully, but these errors were encountered: