# Feature SI-117 - Accept client credentials token issued by OIDC IDP

Project: Stream Integration Basics
Status: closed
URL: https://community.openproject.org/work_packages/SI-117

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 16.2.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers | Jan Sandbrink |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator  
**I want to** be able to accept JWTs issued in a client credentials flow,  
**so that** SCIM requests can be authenticated without configuring additional secrets.

**Acceptance criteria**

  - JSON Web Tokens issued to another client can be processed

  - Instead of authenticating an OpenProject user they should authenticate a service account
    
      - The service account is associated to a SCIM-Client

**Technical notes**

  - It probably makes sense to understand and think about the general concepts involved in authentication

  - The service account should probably inherit from principal

**QA notes**

  - This is not independently testable

  - It will probably become sufficiently testable once we have a UI to setup SCIM clients (see <mention class="mention" data-id="62516" data-type="work_package" data-text="#62516">\#62516</mention> )

  - Alternatively we can try to prepare/hack something on QA and then you can try to break what we hacked together
