App Connector Catalog
Twenty pre-built SAML 2.0 and OIDC integration templates for popular self-hosted applications. The catalog is embedded in the Application Registration Wizard — select a connector, supply your deployment domain, review the pre-filled SAML endpoints and attribute mappings, and save.
Overview
The App Connector Catalog removes the need to hand-craft service provider metadata for common applications. Each catalog entry is a parameterised template — you fill in your deployment's domain, and Hawiyati generates the correct SAML metadata or OIDC client configuration and registers it in the SP registry in a single operation.
Templates are seeded from YAML files bundled in hawiyati-admin at startup. They are stored in the hawiyati_config.connector_templates database table and exposed through the Application Registration Wizard in the Admin Console and the REST API at /api/v1/catalog.
The catalog is integrated directly into the Application Registration Wizard. When you click Register Application in the Applications page, you choose between browsing the catalog (templates pre-fill all endpoints) or configuring a custom SAML 2.0 or OIDC integration from scratch. Both paths produce a standard SP registry entry.
No cloud accounts or vendor portals are required. Run Grafana, GitLab, Vault, and the other tools on your own infrastructure and point the connector at your instance domain.
Available connectors
The catalog ships with 20 connectors across six categories.
Monitoring
| Connector | Protocol | Notes |
|---|---|---|
| Grafana | SAML 2.0 | Dashboard and alerting platform. SAML SSO via built-in auth proxy. |
| Kibana | SAML 2.0 | Elasticsearch visualisation. Requires Elastic security plugin. |
| Prometheus | OIDC | Metrics server. OIDC reverse-proxy pattern via oauth2-proxy sidecar. |
DevOps
| Connector | Protocol | Notes |
|---|---|---|
| GitLab CE/EE | SAML 2.0 | Git hosting and CI/CD. SAML login under Admin > Settings > SSO. |
| Jenkins | SAML 2.0 | Build automation server. Requires SAML plugin. |
| SonarQube | SAML 2.0 | Code quality platform. SAML configured in sonar.properties. |
| Nexus Repository | SAML 2.0 | Artifact repository. SAML IDP-initiated supported from v3.38. |
| Gitea | OIDC | Lightweight Git hosting. OIDC OAuth app under Site Administration. |
Productivity & Collaboration
| Connector | Protocol | Notes |
|---|---|---|
| Nextcloud | SAML 2.0 | File sharing and groupware. SAML via SSO & SAML authentication app. |
| Mattermost | SAML 2.0 | Team messaging. SAML under System Console > Authentication. |
| Rocket.Chat | SAML 2.0 | Open-source messaging. SAML under Administration > SAML. |
| Seafile | SAML 2.0 | Document collaboration. SAML requires seahub_settings.py changes. |
| Jitsi Meet | SAML 2.0 | Video conferencing. SAML via Prosody LDAP/SAML bridge. |
Infrastructure
| Connector | Protocol | Notes |
|---|---|---|
| Rancher | SAML 2.0 | Kubernetes management UI. SAML under Users & Authentication > Auth Provider. |
| Kubernetes Dashboard | OIDC | K8s web UI. OIDC proxy or kube-apiserver OIDC flags. |
| Portainer | OIDC | Container management. OAuth/OIDC under Settings > Authentication. |
Security & Secrets
| Connector | Protocol | Notes |
|---|---|---|
| HashiCorp Vault | OIDC | Secrets management. OIDC auth method under vault auth enable oidc. |
Business & Documentation
| Connector | Protocol | Notes |
|---|---|---|
| Odoo | SAML 2.0 | ERP platform. SAML via social-auth-saml module. |
| Redmine | SAML 2.0 | Project management. SAML via omniauth-saml plugin. |
| Zammad | SAML 2.0 | Help desk ticketing. SAML under Admin > Security > Third-party applications. |
| BookStack | SAML 2.0 | Wiki platform. SAML under Settings > Authentication. |
Registering an application from the catalog
The catalog is accessed through the Application Registration Wizard in the Admin Console. There is no standalone "App Catalog" sidebar page — catalog templates are a path inside the same wizard used for custom SAML and OIDC registrations.
Wizard walkthrough
- Open the wizard. Navigate to Identity & Access > Applications and click Register Application. The wizard opens on the Choose step.
- Browse App Catalog. Click the Browse App Catalog card. The wizard advances to the Pick App step, showing all connectors as tiles filterable by name and category.
- Select the connector. Click the application tile (e.g., Grafana, Odoo). A green checkmark marks the selection, and the Next button activates.
- General — name and domain. Enter the application display name and your deployment domain (host only, no scheme or trailing slash). The wizard shows a preview of the entity ID that will be generated from your domain.
- Sign-On — review SP endpoints. Entity ID, ACS URL, SLO URL, NameID format, and signing options are pre-filled from the template with your domain substituted. Edit any field that differs from your deployment.
- Attribute statements. User attributes to include in SAML assertions are pre-filled from the template. Add, remove, or change mappings as needed.
- Access & policy. Optionally assign an authentication policy, restrict accepted authentication methods, enable JIT provisioning, and require KYC verification for this application.
- Review and save. Inspect all settings. Click Save Application. Hawiyati creates the SP registry entry and displays the Setup Instructions panel with the IdP Metadata URL and SSO URL to paste into the application's SAML configuration.
Enter the host and optional port only — for example grafana.example.org or gitlab.example.org:8443. Do not include https:// or a trailing slash. The connector template prepends the scheme and constructs the full endpoint URL.
The Setup Instructions panel shows Hawiyati's IdP Metadata URL (https://<idp-host>/saml/metadata). Paste this URL into your application's SAML Identity Provider configuration. Applications that support metadata auto-import (Grafana, GitLab, Nextcloud) will download the certificate and SSO URL automatically.
Template parameters
Every connector template uses two standard parameters. Some connectors add a third.
| Parameter | Required | Description |
|---|---|---|
domain | Yes | Host (and optional port) where the application is running. Example: grafana.example.org. |
displayName | Yes | Human-readable name shown in the SP registry and the login chooser. Defaults to the connector name. |
instanceId | OIDC only | Suffix appended to the generated OIDC client ID. Allows multiple instances of the same application to coexist. Defaults to the connector slug. |
REST API
The catalog is also accessible programmatically via the Admin API. All endpoints require an authenticated admin session.
| Method | Path | Description |
|---|---|---|
GET | /api/v1/catalog | List all connector templates. |
GET | /api/v1/catalog/{slug} | Get a single connector template by slug. |
POST | /api/v1/catalog/{slug}/enable | Enable a connector. Body: {"domain":"…","displayName":"…"}. Returns 201 Created on success. |
Example — enable Grafana via the API:
POST /api/v1/catalog/grafana/enable
Content-Type: application/json
{
"domain": "grafana.example.org",
"displayName": "Grafana"
}
Adding custom connectors
The catalog is extensible. To add a connector for an application not in the built-in list:
- Create a YAML file in
hawiyati-admin/src/main/resources/connectors/following the schema of an existing connector file. Use{{domain}}and{{displayName}}as placeholders. - Restart
hawiyati-admin. TheConnectorCatalogSeederapplication runner picks up the new file on startup and inserts it into the database if the slug does not already exist. - The connector immediately appears in the Admin Console catalog and the REST API.