# Bug SI-91 - Trying to create OIDC user tokens, even for non-OIDC providers

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 15.4.0 |
| Observed in versions | 15.3.0 |
| Bug found in version (deprecated) | 15.3.x |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Jan Sandbrink |
| 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 via non-OIDC provider

2.  Check log messages of the Rails application

### What is the buggy behavior?

You can see the following message for each login:

``` text
Could not associate token to user: No access token
```

This indicates that we try to create OIDC user tokens, even if the provider is not an actual OIDC provider.

### What is the expected behavior?

We should only attempt to create OIDC user tokens when logging in through OIDC.

### QA Note

I think you can't really test that the extra call is not made. What you can double check is that the login still works for all kinds of users: Internal login, Login via different OIDC providers and (if we have set that up) login via SAML.
