authentik/website/integrations/hypervisors-orchestrators/xen-orchestra/index.md at e7fcfb7e67d5df3e8a8a5da170f18fa4c6b98731

mirror of https://github.com/goauthentik/authentik synced 2026-04-27 09:57:31 +02:00

Files

Teffen Ellis 6ed5cb5249 website/docs: Modal and wizard button labels (#21549 )

* website/integrations: rename "Create with Provider" to "New Application"

The application list page now uses a split-button labeled
"New Application" instead of the old "Create with Provider" dropdown.
Update all 113 integration guides to match.

* website/docs: update flow, stage, and policy button labels

- "Create" → "New Flow", "New Stage", "New Policy" for trigger buttons
- "Finish" → "Create Flow", "Create Stage", "Create Policy" for submit
- "Create and bind stage" → "New Stage" / "Bind Existing Stage"
- "Create" (binding submit) → "Create Stage Binding"

* website/docs: update provider button labels

- "Create" → "New Provider" for trigger buttons
- "Create with Provider" → "New Application" in RAC docs
- "Create" → "New Property Mapping", "New RAC Endpoint", "New Prompt"
  for related entity creation

* website/docs: update directory button labels

- "Create" → "New Source" for federation/social login pages
- "Create" → "New Role", submit → "Create Role"
- "Create" → "New Invitation"
- Policy binding submit → "Create Policy Binding"

* website/docs: update endpoint device and system management button labels

- "Create" → "New Endpoint Connector", "New Enrollment Token",
  "New Device Access Group", "New Flow"
- Submit → "Create Device Access Group"
- "Create" → "New Notification Rule", "New Notification Transport"
- Binding submit → "Create Policy Binding"

* Reorganize policy documentation

* website/docs: address policy docs review feedback

* post-rebase

* website/docs: Reorganize policy documentation -- Revisions (#21601)

* apply suggestions

* Fix escaped.

* Fix whitespace.

* Update button label.

* Fix phrasing.

* Fix phrasing.

* Clean up stragglers.

* Format.

---------

Co-authored-by: Dominic R <dominic@sdko.org>

2026-04-16 17:35:38 +00:00

3.6 KiB

Raw Blame History

title, sidebar_label, support_level

title	sidebar_label	support_level
Integrate with Xen Orchestra	Xen Orchestra	community

What is Xen Orchestra

Xen Orchestra provides a user friendly web interface for every Xen based hypervisor (XenServer, xcp-ng, etc.).

-- https://xen-orchestra.com/

:::info Xen Orchestra offers authentication plugins for OpenID Connect, SAML and LDAP. This guide is using the OpenID Connect plugin. If you are using the Xen Orchestra Appliance, the OIDC Plugin should be present. If you are using Xen Orchestra compiled from sources, make sure the plugin auth-oidc is installed. :::

Preparation

The following placeholders are used in this guide:

xenorchestra.company is the FQDN of the Xen Orchestra instance.
authentik.company is the FQDN of the authentik installation.

:::info This documentation lists only the settings that you need to change from their default values. Be aware that any changes other than those explicitly mentioned in this guide could cause issues accessing your application. :::

authentik configuration

To support the integration of Xen Orchestra with authentik, you need to create an application/provider pair in authentik.

Create an application and provider in authentik

Log in to authentik as an administrator and open the authentik Admin interface.
Navigate to Applications > Applications and click New Application to open the application wizard.

Application: provide a descriptive name, an optional group for the type of application, the policy engine mode, and optional UI settings.
Choose a Provider type: select OAuth2/OpenID Connect as the provider type.
Configure the Provider: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Note the Client ID, Client Secret, and slug values because they will be required later.
- Set a Strict redirect URI to https://xenorchestra.company/signin/oidc/callback.
- Select any available signing key.
Configure Bindings (optional): you can create a binding (policy, group, or user) to manage the listing and access to applications on a user's My applications page.

Click Submit to save the new application and provider.

Xen Orchestra configuration

Xen Orchestra allows the configuration of the OpenID Connect authentication in the plugin-section. All of the URLs mentioned below can be copied & pasted from authentik (Applications > Providers > the provider created earlier).

Navigate to Settings > Plugins
Scroll to auth-oidc and click on the + icon on the right hand side.
Configure the auth-oidc plugin with the following configuration values:

Set the Auto-discovery URL to https://authentik.company/application/o/xenorchestra/.well-known/openid-configuration.
Set the Client identifier (key) to the Client ID from your notes.
Set the Client secret to the Client Secret from your notes.
Check the Fill information (optional) checkbox to open the advanced menu.
Set the Username field to username
Set the Scopes to openid profile email

Enable the auth-oidc-Plugin by toggling the switch above the configuration.
You should be able to log in with OIDC.

:::info The first time a user signs in, Xen Orchestra will create a new user with the same username used in authentik. If you want to map the users by their e-mail-address instead of their username, you have to set the Username field to email in the Xen Orchestra plugin configuration. :::

3.6 KiB Raw Blame History