authentik/website/integrations/infrastructure/osticket/index.md at e7fcfb7e67d5df3e8a8a5da170f18fa4c6b98731

mirror of https://github.com/goauthentik/authentik synced 2026-04-27 18:07:15 +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.9 KiB

Raw Blame History

title, sidebar_label, support_level

title	sidebar_label	support_level
Integrate with osTicket	osTicket	community

What is osTicket

osTicket is a web-based, open source user support/ticketing solution.

-- https://osticket.com

Preparation

The following placeholders are used in this guide:

osticket.company is the FQDN of the osTicket installation.
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 osTicket with authentik, you need to create an application/provider pair 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://osticket.company/osticket/api/auth/oauth2.
  - Select any available signing key.
  - Under Advanced protocol settings:
    - Subject Mode: Based on the User's Email
- 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.

osTicket configuration

Download the OAuth2 plugin from the osTicket website and place it into the include/plugins folder of your osTicket installation.
Log in to osTicket as an administrator and navigate to the Admin Panel.
Navigate to Manage > Plugins.
Click Add New Plugins and follow the on-screen instructions to install the OAuth2 plugin.
Once installed, click on the newly installed OAuth2 plugin, set Status to Active, then click Save Changes.
Navigate to Instances, click on Add New Instance, select OAuth2 - Other, and set the following fields:
- On the Instance tab:
  - Set a Name.
  - Set Status to Enabled.
- On the Config tab:
  - Name: authentik
  - Authentication Target: Agents Only or End Users Only or Agents and End Users
  - Authentication Label: authentik
  - Redirect URI: https://osticket.company/osticket/api/auth/oauth2
  - Client Id: Set the Client ID from authentik.
  - Client Secret: Set the Client secret from authentik.
  - Authorization Endpoint: https://authentik.company/application/o/authorize/
  - Token Endpoint: https://authentik.company/application/o/token/
  - Resource Details Endpoint: https://authentik.company/application/o/userinfo/
  - Scopes: email openid profile
Click on Save Changes.

Configuration verification

To verify that authentik is correctly integrated with osTicket, first log out of your account. Then, log back in using the Sign in with authentik button. You should be redirected to your authentik instance and after successfully authenticating, you should be redirected to osTicket and logged in.

Resources

osTicket Docs - OAuth2 Guide

3.9 KiB Raw Blame History