[dev.icinga.com #9074] Basic API framework

[icinga-migration]

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

Created by gbeutner on 2015-04-17 12:17:07 +00:00

Assignee: (none)
Status: Closed (closed on 2015-09-28 12:42:58 +00:00)
Target Version: 2.4.0
Last Update: 2015-11-06 17:13:01 +00:00 (in Redmine)

Backport?: No
Include in Changelog: 0

---

• API uses HTTPS
• TCP socket (listens on 127.0.0.1:5665 by default, shared with the cluster framework), TLS
  • Enabled by default
  • an X.509 certificate is auto-generated when Icinga 2 is first installed
• Authentication using usernames and passwords
  • authentication request with user password
  • Implement 'ApiUser' object
  • attributes: password, client_cn
  • Protect the api_password by blocking the getter
  • Implement check_password function
  • Auto-generate 'root' user when Icinga 2 is installed
  • Support for client certificates
• authorization
  • Attributes: api_permissions
  • Grant basic permissions based on API commands, e.g.
    • commands.acknowledge
    • commands.enable_active_checks
    • commands.*

Changesets

2015-09-30 06:41:09 +00:00 by (unknown) 7e4953d

Improve log messages for HTTP requests

refs #9074

---

Subtasks:

• Feature 9084 - Enable the ApiListener by default
• Feature 9085 - Certificate-based authentication for the API
• Feature 9086 - Password-based authentication for the API
• Feature 9087 - Create default administrative user
• Feature 9088 - API permissions
• Feature 9076 - Reflection support for the API
• Feature 9447 - Implement support for HTTP
• Feature 9448 - Define RESTful url schema
• Feature 9471 - Implement ApiUser type
• Feature 9470 - Implement URL parser

[icinga-migration]

Updated by gbeutner on 2015-04-17 12:57:55 +00:00

• Description updated

[icinga-migration]

Updated by gbeutner on 2015-04-17 12:58:40 +00:00

• Description updated

[icinga-migration]

Updated by gbeutner on 2015-04-17 12:59:18 +00:00

• Blocks set to 9075

[icinga-migration]

Updated by mfriedrich on 2015-06-18 11:42:58 +00:00

• Description updated

[icinga-migration]

Updated by MarkusR on 2015-06-23 11:32:56 +00:00

Will it be possible to write passive check results via the new API?

I see two use cases:

1. For Windows i2 instances because currently there is currently no possibility to send passive check results under Windows .
2. Replacement of nsca (or nsca-ng). Maybe it is possible to additional compile a small binary similar to send_nsca.

[icinga-migration]

Updated by gbeutner on 2015-08-15 17:57:30 +00:00

• Blocks deleted 9075

[icinga-migration]

Updated by mfriedrich on 2015-09-28 12:42:58 +00:00

• Status changed from New to Closed

[icinga-migration]

Updated by gbeutner on 2015-09-29 06:11:11 +00:00

• Backport? changed from TBD to No

[icinga-migration]

Updated by gbeutner on 2015-11-06 17:13:01 +00:00

• Include in Changelog changed from 1 to 0