# SSO login and Jobs::EnsureDbConsistency both fail
**URL:** https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515
**Category:** Bug
**Created:** [January 10, 2017, 7:15pm UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515 "2017-01-10T19:15:34Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [January 10, 2017, 7:15pm UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/1 "2017-01-10T19:15:34Z")
I have two sites having SSO enabled. After the latest update, both of them started failing SSO logons for moderators and admins (but not for normal users), with a localized error message that is similar to “name is already being used”:
```plaintext
Verbose SSO log: Record was invalid: Group 3
{:name=>"wird bereits verwendet"}
nonce: ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
name: Felix Freiberger
username: felix.freiberger
email: ■■■■■■■■■■■■■■■■■■■■■■■■
avatar_url:
avatar_force_update:
require_activation: true
bio:
external_id: 14
return_sso_url:
admin: true
moderator: true
suppress_welcome_message:
add_groups:
remove_groups:
```
More intriguingly, the logs also contain failures for `Jobs::EnsureDbConsistency`. They look like this:
```plaintext
Job exception: Validierung gescheitert: Name wird bereits verwendet
```
```plaintext
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:79:in `raise_record_invalid'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/validations.rb:43:in `save!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/attribute_methods/dirty.rb:29:in `save!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `block in save!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:351:in `block in with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `block in transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/transaction.rb:184:in `within_new_transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract/database_statements.rb:213:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:220:in `transaction'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:348:in `with_transaction_returning_status'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/transactions.rb:291:in `save!'
/var/www/discourse/app/models/group.rb:224:in `refresh_automatic_group!'
/var/www/discourse/app/models/group.rb:248:in `block in refresh_automatic_groups!'
/var/www/discourse/app/models/group.rb:247:in `each'
/var/www/discourse/app/models/group.rb:247:in `refresh_automatic_groups!'
/var/www/discourse/app/models/group.rb:234:in `ensure_consistency!'
/var/www/discourse/app/jobs/scheduled/ensure_db_consistency.rb:8:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'
```
Since my SSO source hasn’t been updated and the internal check job fails, too, I think this is a Discourse bug.
* * *
Group 3 is the “staff” group (which is called “mitarbeiter” in German).
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [January 17, 2017, 4:22pm UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/2 "2017-01-17T16:22:23Z")
Something is messed up with the group names probably due to localizations.
Any ideas here @tgxworld
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [January 17, 2017, 4:46pm UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/3 "2017-01-17T16:46:03Z")
I just found out that I also cannot revoke a user’s moderator permissions – this gives a `422 error`, and the same error message is sent to `/logs`.
Upgrading to the latest beta didn’t change that.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [January 18, 2017, 2:38am UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/4 "2017-01-18T02:38:47Z")
Can you check through the list of your group names and see if there is already a group with a similar name?
EDIT: Ooo nevermind I have a repro. Will fix.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [January 18, 2017, 3:01am UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/5 "2017-01-18T03:01:06Z")
Ok in Meta’s case, the german translation for staff is “team” and we already have a group named team.
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [January 18, 2017, 5:50am UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/6 "2017-01-18T05:50:14Z")
There are two problems that I uncovered after the investigation.
First, the automatic group names are updated whenever the default locale of the forum is changed. However, the default automatic group names for each locale may be similar to the name of an existing group which is the cause of the `Name has been taken` error. The fix for this is pretty straight forward, if the localized name has already been taken, we simply fallback to the default name for that automatic group.
[https://github.com/discourse/discourse/pull/4662/commits/59dfb51a35ce37c91d34e9c1817c6e536735f1bb](https://github.com/discourse/discourse/pull/4662/commits/59dfb51a35ce37c91d34e9c1817c6e536735f1bb)
Next, a group name change means all the existing group mentions becomes outdated and we don’t have a warning discouraging users from changing group names like how we do for username change.
Instead of implementing the warning, I went ahead and implemented the feature to remap group mentions in all posts whenever a group name is changed.
[https://github.com/discourse/discourse/pull/4662/commits/706b4f6b9faf1f820a294e83f82b0b5a5dba0475](https://github.com/discourse/discourse/pull/4662/commits/706b4f6b9faf1f820a294e83f82b0b5a5dba0475)
---
### Author:  [@fefrei](https://meta.discourse.org/u/fefrei)
#### Post date: [January 18, 2017, 5:53am UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/7 "2017-01-18T05:53:53Z")
Awesome, thanks @tgxworld! Indeed, in both instances with this problem, I do have a group called `team`. Thank you for fixing this ☀
---
### Author:  [@tgxworld](https://meta.discourse.org/u/tgxworld)
#### Post date: [February 20, 2017, 2:56am UTC](https://meta.discourse.org/t/sso-login-and-jobs-ensuredbconsistency-both-fail/55515/9 "2017-02-20T02:56:49Z")