Skip to content
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.

[dev.icinga.com #728] User disabled checkbox should be grayed out if not functional #144

Closed
icinga-migration opened this issue Aug 17, 2010 · 4 comments

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/728

Created by bschmidt on 2010-08-17 10:21:25 +00:00

Assignee: jmosshammer
Status: Resolved (closed on 2011-09-27 11:20:29 +00:00)
Target Version: 1.14
Last Update: 2015-10-26 08:34:29 +00:00 (in Redmine)

Icinga Version: 1.13.3
Icinga Web Version: 1.13.1
IDO Version: 1.13.0
OS Version: any
DB Type: UNKNOWN
DB Version: --
Browser Version: --

In case of chosen LDAP auth the checkmark in the "User disabled" checkbox seems to be useless.

That means the user is still able to login if checked.

The visual state should represent that.

Changesets

2011-09-27 11:14:55 +00:00 by jmosshammer 925667b

* Invalid button is hidden when not available (fixes #728)

2015-10-20 12:23:43 +00:00 by mhein 467ee5b

Add store trigger to disfunctional fields in user mgt

fixes #728

2015-10-20 12:26:52 +00:00 by mhein ca70511

Add store trigger to disfunctional fields in user mgt

fixes #728
@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-26 14:58:55 +00:00

  • Category set to Usermanagement
  • Target Version set to 1.6

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-27 10:01:13 +00:00

  • Assigned to set to jmosshammer

@icinga-migration
Copy link
Author

Updated by jmosshammer on 2011-09-27 11:20:29 +00:00

  • Status changed from New to Resolved
  • Done % changed from 0 to 100

Applied in changeset 925667b.

@icinga-migration
Copy link
Author

Updated by mfriedrich on 2015-10-26 08:34:29 +00:00

  • Target Version changed from 1.6 to 1.14
  • Icinga Version set to 1
  • Icinga Web Version set to 1
  • IDO Version set to 1
  • OS Version set to any
  • DB Type set to UNKNOWN
  • DB Version set to --
  • Browser Version set to --

This was never really resolved according to Marius, therefore re-assigning the fixed issue to the next release target.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant