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

Can't rename users full name - Authentication error #11057

Closed
camoflash opened this issue Sep 5, 2018 · 3 comments
Closed

Can't rename users full name - Authentication error #11057

camoflash opened this issue Sep 5, 2018 · 3 comments

Comments

@camoflash
Copy link

camoflash commented Sep 5, 2018

Steps to reproduce

  1. Open any browser, log into nextcloud as an Administrator and go to page where you can edit all users
  2. Open browser's Inspector tool -> Network tab
  3. Edit user's 'Full Name' field
  4. Look for POST Request named displayName in Inspector tool
  5. Look at the POST Request response
  6. Reload page to see if 'Full Name' field is changed

Expected behaviour

  • Dialog box asking for password confirmation before changes to user's 'Full Name' field is commited
  • POST Request "displayName" getting a good response
  • Reloading page should have shown changes to user's 'Full Name' field

Actual behaviour

Tell us what happens instead

  • No password confirmation dialog appearing
  • POST Request is returning the response: {"status":"error","data":{"message":"Authentication error"}}
  • Reloading page does not show any change to user's 'Full Name' field

Server configuration

Operating system:
Ubuntu 18.04

Web server:
Nginx

Database:
mysql

PHP version:
7.2

Nextcloud version: (see Nextcloud admin page)
13.5

Updated from an older Nextcloud/ownCloud or fresh install:
Updated from ealier 13 version only

Where did you install Nextcloud from:
Nextcloud docker: https://github.com/nextcloud/docker

Signing status:

Signing status No errors have been found.

List of activated apps:

App list
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

Config report
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or 

Insert your config.php content here. 
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using external storage, if yes which one: local/smb/sftp/...

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

LDAP configuration (delete this part if not used)

LDAP config
With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your Nextcloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';


Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration

Browser:
Firefox 61.0.2, Chrome 68.0.3440.106
Operating system:
Windows 10

Logs

Web server error log

Web server error log
Insert your webserver log here

Nextcloud log (data/nextcloud.log)

Nextcloud log
Insert your Nextcloud log here

Browser log

Browser log
Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...
@nextcloud-bot
Copy link
Member

GitMate.io thinks possibly related issues are #772 (LDAP Users not mapped and authentication fails), #272 (LDAP Users not mapped and authentication fails), #1011 (Error while re-creating a user), #9170 (redirect), and #8241 (image).

@MartB
Copy link
Member

MartB commented Sep 6, 2018

Can not reproduce on 14.0.0 RC 2 so i would assume it has been fixed since then.
Will try to find the fix so it can be backported.

Edit:
I did not know that the entire js stuff was rewritten.
Will leave this to someone that is more familiar with the codebase.

@MorrisJobke
Copy link
Member

I did not know that the entire js stuff was rewritten.
Will leave this to someone that is more familiar with the codebase.

Not likely to be back ported as we moved to a completely new code basis. Sorry for that. I would close this for now.

If you have still problems: could you try the provisioning API to update the display name and check also the logs for suspicious entries? We then can reopen the issue.

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

4 participants