# Bug SI-184 - ScimClient access token and client credentials dialogs render wrong value

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | API / SCIM |
| Target versions | 16.2.0 |
| Observed in versions |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Pavel Balashou |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Login as an admin.
    
2.  Go to the ScimCleint creation form.
    
3.  Choose &quot;Static access token&quot;.
    
4.  Click on create.
    
5.  You see downcased hash value like: `3804c29949ed1d14eb70bd0056b31b6cb146cc72a5f3b55bca8146887f606228`
    

UPD: the same problem is actual for ScimClient with OAuth credentials (`client_secret` filed)

### What is the buggy behavior?

*   Not original plaintext token is presented to the admin for copying.
    
*   ScimClient fails to authenticate in OP SCIM Server API due to the wrong value presented to the admin. &nbsp;
    

### What is the expected behavior?

1.  Access token and OAuth client secret must be presented in plain text format, not hashed. Usually it looks like: `FVz-fQlyY9IwvL-NkfEm8KD6z9qUGbvSIOi_nwJuDEU` (there are upcase, downcase and special chars used)
    
2.  Presented access token is accepted by SCIM API.
