GitLab

This allows support for SSO userIDs. Only the admin can set
usernames greater than 30 characters.

Bug #548165

Change-Id: Ib5a8b1cbda7808fd6b1780f87a9a52a3443712c8
Signed-off-by: Hugh Davenport <hugh@catalyst.net.nz>

This is to allow the uploadcsv function to honour the 'Force password change?' selection

Change-Id: I085b257ecb02d38185615f23dcd7534682311a3d
Signed-off-by: Darryl Hamilton <darrylh@catalyst.net.nz>

Change-Id: I894c1c2b7859bd198a5a89218ceabea0cd547b7a
Signed-off-by: Richard Mansfield <richard.mansfield@catalyst.net.nz>

Change-Id: Ie203de378ddb3af9248c7dcf17cd304c7775abe0
Signed-off-by: Darryl Hamilton <darrylh@catalyst.net.nz>

* encrypt passwords on user add, edit and imports
* upgrade to encrypt and add salt to all existing cleartext passwords
* update validate_password to prevent successful validation of cleartext passwords with no salt
Signed-off-by: Eugene Venter <eugene@catalyst.net.nz>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>
(cherry picked from commit 627dd3d8083e0b6ba06440eabebc055c8ba4ba78)

now each plugin can say whether it can be disabled or not. defaults to true

Allow usernames to contain many more characters than they do currently when using internal authentication.

The previous restrictions were unnecessarily strict. As per request from MyPortfolio.

Now we actually can has a Mjollnir`!
(cherry picked from commit 36a1ecfc)

The name is largely irrelevant as it's only the creator of the file.

If an authentication plugin thinks that a user should be able to log in, and furthermore thinks that it is able/allowed to automatically create user accounts, then it is now able to do just that. The authentication API now has a new method - can_auto_create_users() - to define whether each authentication instance feels it can/should be able to do this.

If the instance thinks it can, it needs to export some information through the get_user_info method in order to populate the user account. Although this may change shortly to be optional, with the users instead being forced to enter any information that is required that they haven't otherwise filled out.

Signed-off-by: Andrew McMillan

code

actual username

couple of unnecessary auth methods. Make sure also to say the internal auth
method does not have configuration.

generates the form)

suspension is an internal-only thing. Changed the change_password function
to take a username instead of a user object. Moved the is_username_valid
function nearer to the bottom, as it's not part of the authentication api
as such.

  - check if a user is suspended, and if so return some information about
    it
  - change a users password to the given password

Removed the implementation of get_user_info, which is no longer needed now
that by default information is sourced from the database by the
authentication stuff.

PHP side.

usernames/passwords are valid. Made the encrypt_password method public, so
it can be used when changing the password for a user. Use 'self' instead of
a broken class name.

be removed.

and fixed up references to Auth_* classes.