Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
that it's not hardcoded to return the user with id 2. Create
user::admin_user() which finds an appropriate admin and returns it.
Fixes #1358.
|
|
- add_user_to_group and remove_user_from_group should take Group_Definition instances
to be consistent
- add_user_to_group and remove_user_from_group in drivers/IdentityProvider.php should
not be static
|
|
|
|
a required
parameter for the Gallery driver.
|
|
|
|
|
|
|
|
the identity provider isn't writable, the method implementations should throw an Invalid Operation exception.
|
|
IdentityProvider interface.
|
|
|
|
changing providers.
|
|
Create a helper class called identity to simplify call the Identity Provider. Move the contents of MY_Session.php to the new helper class and remove the MY_Session class
|
|
|
|
to use it to get the group it is modifying
|
|
access_Core::_get_all_groups() to use this to get the defined groups.
|
|
What I've tested to this point, is you can install a new provider, switch to it, login as administrator, uninstall the default user module, reinstall the user module, switch back to the user module and login.
|
|
the user module
Bagging the User_Definition and Group_Definition abstract classes and replacing them with interfaces with the same names.
Make sure all the unit tests work.
|
|
redundant code in the user module and remove references to the Identity helper from the user module as the user module should be able to access things directly. Simplify the get_user_list api method to just accept an array of ids to return user objects for.
|
|
be active at a given time.
|
|
|
|
Conflicts:
modules/gallery/controllers/admin_users.php
modules/gallery/controllers/password.php
modules/gallery/helpers/group.php
modules/gallery/helpers/user.php
modules/notification/helpers/notification.php
|
|
classes which extend the User_Definition and Group_Definition classes defined in the Identity API
|
|
for event notifications. This drove out some issues in the user::users and
group::groups API backend.
|
|
Identity/Gallery::list_groups
|
|
|
|
Create an Identity library that defines the interface the Gallery3 expects
Move the user and group helpers into the gallery module to provide the familiar
interface into the Identity library.
Create a Gallery Identity back-end that is supplied by the user module.
The vision here is that all user and group code that is gallery or ui specific
is contained within the core product. Anything that relates to manipulating a
user or group is contained in the back end code that can be replaced.
|
|
consistency. No 3rd party libs in "libraries", at least for now.
|
|
html for the login form is retrieve via an ajax call when the user clicks on login. Can't login with a valid id yet, but you certainly get error messages when things are wrong :-)
|
|
login link in the header wil open up a login box like the mockup
|
|
file_structure_test
|
|
mechanism as g1 and g2 to facilitate a migration.
|
|
|
|
based on the contents of the user/config/user.php file. And load that driver based on the User_Driver interface. There is a default User_Gallery_Driver class that will provide the actual interface implementation. Replacing this driver will allow a completely different user and authentication implementation to be used... hopefully will reduce issues with embedding and other user management systems. Removed from unit tests so they will still run.
|