Skip to content
This repository has been archived by the owner. It is now read-only.

[dev.icinga.com #2456] Credential for CustomCronks #720

Closed
icinga-migration opened this issue Mar 19, 2012 · 2 comments
Labels

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Mar 19, 2012

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

Created by mhein on 2012-03-19 13:58:32 +00:00

Assignee: mhein
Status: Resolved (closed on 2012-03-20 11:22:10 +00:00)
Target Version: (none)
Last Update: 2012-03-26 11:10:37 +00:00 (in Redmine)


Explicit allow saving custom Cronks.

Changesets

2012-03-20 11:16:24 +00:00 by mhein abbda19

* Added credential for editing custom cronks (fixes #2456)

2012-03-26 10:01:33 +00:00 by mhein f6f8e1b

* Added credential for editing custom cronks (fixes #2456)
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Mar 20, 2012

Updated by mhein on 2012-03-20 11:22:10 +00:00

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

Applied in changeset abbda19.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Mar 26, 2012

Updated by mhein on 2012-03-26 11:10:37 +00:00

The credential is "explicit" ... Means:

On a new installation the right will be created and assigned to default group "icinga_user".

If you do this by upgrading your DB from 1.6.2 to 1.7 you have to assign right "icinga.cronk.custom" to any group/user to let user save and edit their custom cronks again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
1 participant
You can’t perform that action at this time.