-
Notifications
You must be signed in to change notification settings - Fork 66
reset environment fails with api errors #869
Comments
@kbsingh have you seen this with any other user? |
@aslakknutsen can you please look into this. |
It seems the users oso token stored in keycloak was no longer valid, so the tenant service was failing. Would it be possible for the tenant service to report through to the UI something better? And maybe even redirect the user to a page where they can relink their account from oso ? |
@kbsingh yes, we are planning to address it. The corresponding issue on Auth side - fabric8-services/fabric8-auth#38 |
@alexeykazakov is this a bug with one user or a bug for everyone? If it is just one user then we should move the issue. |
@joshuawilson it's a very old issue. Sometimes for whatever reason OSO tokens get invalid. We don't know why. OSO team doesn't know either. It happen with different users. |
@alexeykazakov curious regarding why we marked this issue as not a bug. This is not expected behaviour is it? |
In this case the reset env failed because the OSO token was invalid. It’s expected behavior to fail in such case. It’s rather a missing feature to auto detect invalid OSO tokens. |
This sounds like a request for a new feature, so I'm going to type/feature for now. Also, when bug was removed severity was not, so I'll do that, too. |
@alexeykazakov This is technically /api/user/services not replying with propper www-auth challenge headers based on response from auth, and UI not understanding it if it did.. :) |
For user drc01inb, trying to reset env I get, the Your account section :
The configs are not updated for che/jenkins
The text was updated successfully, but these errors were encountered: