# Error updating user preferences. Credentials not provided? **URL:** \ **Category:** Development\ **Created:** [October 7, 2019, 2:33pm UTC](https://discuss.openedx.org/t/error-updating-user-preferences-credentials-not-provided/643 "2019-10-07T14:33:44Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![vrios](https://avatars.discourse-cdn.com/v4/letter/v/e495f1/32.png) [@vrios](https://discuss.openedx.org/u/vrios)\ **Post date:** [October 30, 2019, 2:28pm UTC](https://discuss.openedx.org/t/error-updating-user-preferences-credentials-not-provided/643/3 "2019-10-30T14:28:34Z")
We have a working fix using badgr-server without needing any model changes!! 🎉. On badgr server code/apps/mainsite/settings.py go to middleware classes and remove/comment ‘badgeuser.middleware.InactiveUserMiddleware’, Now go to badgr server /code/apps/issuer/admin.py and remove entity\_id from the readonly fields of BadgeClassAdmin. You would have to edit the slug using the barebones interface(can’t figure out the commit that made entity\_id field readonly on badgr-ui). Once it is editable you can make it match the query edx sends once a particular badge is earnt. Badge queries sent by edx follow the format openedx\_\_coursebadgeslug provided that openedx\_\_course is used as a issuing component and badgeslug is the slug we have defined for this badge class on edx from the admin panel. I would expect the queries to follow the pattern of issuing componentbadgeslug if you don’t use openedx\_\_course as an issuing component but I am afraid to test it out after seeing some odd behaviour when testing similar functionalities. The solution described above, 2 single statement file changes on a badgr server instalation, works like a charm and doesnt kick the user out after earning a badge --- _[View the full topic](https://discuss.openedx.org/t/error-updating-user-preferences-credentials-not-provided/643)._