When closing the dialog, we cancel the cancellable, but don't
wait for all the async calls to complete before closing the dialog
so discard results when they come in.
https://bugzilla.gnome.org/show_bug.cgi?id=700958
When an enterprise login user account is disabled, or needs to have
its password change, just prompt for the administrator to do the join
to the domain. This is exactly the same fall through as if the user
does not have permission to join a machine to a domain.
https://bugzilla.gnome.org/show_bug.cgi?id=699293
If we discover domains again, don't add them twice to the drop
down and confuse the user. This is especially important if we
receive two realms from realmd for the same domain for use with
different clients (ie: sssd/winbind). We only want to offer the
first choice
https://bugzilla.gnome.org/show_bug.cgi?id=686397
* DBus interface was reviewed and there were several things added
to make it more generic and useful for other realm types.
* Use ObjectManager to track objects in realmd. This facilitates
using realmd with the way it now uses multiple interfaces
on objects.
https://bugzilla.gnome.org/show_bug.cgi?id=682185
* In particular support of different credential methods and better
hints for different owners of those credentials, so we can prompt
more cleanly.
* Less abstraction in the realmd interfaces
https://bugzilla.gnome.org/show_bug.cgi?id=680892
The changes in the realmd dbus interface are futureproofing to
support cancellation.
In addition during this time of interface flux, check the
daemon version number to make sure we can talk to it.
https://bugzilla.gnome.org/show_bug.cgi?id=678105
* Use realmd for domain joining and lookup, runtime dependency
* Validate join domain correctly
* Add UmRealmManager for handling some stuff above the autogenerated
realmd dbus code
* Show a dialog if the user's credentials cannot be used to join
the domain. Prompt for admin creds.
* Register the user's login with the AccountsService
* This depends on the CacheUser() method of AccountsService
https://bugzilla.gnome.org/show_bug.cgi?id=677548
This title makes sense for both remote and local users. In the
case of remote users we're not creating accounts, we're just
adding them to the system.
https://bugzilla.gnome.org/show_bug.cgi?id=677548
More clear scoping and interaction with running actions in
UmAccountDialog. In later 'enterprise login' patches we have long
running actions that's why this needs cleaning up.
In particular:
* Show errors as children of the dialog.
* Errors don't make the account dialog go away, user can correct
problems.
* Use more standard GAsyncResult style callbacks:
um_account_dialog_perform() um_account_dialog_finish()
* Disable controls while the operation is happening.
* Allow the user to cancel long actions in UmAccountDialog by
pressing the cancel button.
https://bugzilla.gnome.org/show_bug.cgi?id=677548
It's confusing to read; it reads as 'user manager'. Since this
is a GObject, just use self as customary.
Most of these lines change in later commits anyway, so this won't
really pollute the 'git blame'
https://bugzilla.gnome.org/show_bug.cgi?id=677548
