summaryrefslogtreecommitdiff
path: root/spec/models/identity_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add latest changes from gitlab-org/gitlab@masterGitLab Bot2020-02-051-1/+1
|
* Add # frozen_string_literal to spec/modelsThong Kuah2019-04-011-0/+2
| | | | Adds `# frozen_string_literal: true` to spec/models ruby files
* Fix failed LDAP logins when nil user_id presentStan Hu2019-01-291-0/+34
| | | | | | | | | | | | | | | | | | | | | When a LDAP user signs in the for the first time and if there is an `Identity` object with `user_id` of `nil`, new users will not be able to be register until that entry is cleared because of the way identities are created: 1. First, the User object is built but not saved, so it has no `id`. 2. Then, `user.identities.build(provider: 'ldapmain')` is called, but it does not have an associated `user_id` as a result. 3. `User#save` is called, but the `Identity` validation fails if an existing entry with `user_id` of `nil` already exists. The uniqueness validation for `nil` values doesn't make any sense in this case. We should be enforcing this at the database level with a foreign key constraint. To work around the issue we can validate against the user instead, which does the right thing even when the user isn't saved yet. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56734
* Fixed user synced attributes metadata after removing current providerFrancisco Javier López2018-02-151-0/+33
|
* LDAP extern_uids are not normalized when updated via APIFrancisco Javier López2017-12-211-0/+27
|
* Changing OAuth lookup to be case insensitiveFrancisco Javier López2017-11-171-0/+10
|
* Normalize LDAP DN when looking up identityDouwe Maan2017-10-311-1/+13
|
* Remove superfluous lib: true, type: redis, service: true, models: true, ↵Rémy Coutable2017-07-271-1/+1
| | | | | | services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me>
* Enable Style/EmptyLines cop, remove redundant onesrubocop/enable-cops-for-empty-linesGrzegorz Bizon2016-07-011-1/+0
|
* Remove the annotate gem and delete old annotationsJeroen van Baarsen2016-05-091-12/+0
| | | | | | | | | In 8278b763d96ef10c6494409b18b7eb541463af29 the default behaviour of annotation has changes, which was causing a lot of noise in diffs. We decided in #17382 that it is better to get rid of the whole annotate gem, and instead let people look at schema.rb for the columns in a table. Fixes: #17382
* Codestyle changesGabriel Mazetto2016-01-121-2/+2
|
* Repair ldap_blocked state when no ldap identity exist anymoreGabriel Mazetto2016-01-081-0/+38