Content
View differences
Updated by Jan Sandbrink about 1 year ago
### 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.
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.