Skip to content
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.

reset environment fails with api errors #869

Open
kbsingh opened this issue Sep 18, 2017 · 10 comments
Open

reset environment fails with api errors #869

kbsingh opened this issue Sep 18, 2017 · 10 comments

Comments

@kbsingh
Copy link
Collaborator

kbsingh commented Sep 18, 2017

For user drc01inb, trying to reset env I get, the Your account section :

Response with status: 500 Internal Server Error for URL: https://api.openshift.io/api/user/services

The configs are not updated for che/jenkins

@joshuawilson
Copy link
Member

@kbsingh have you seen this with any other user?

@joshuawilson
Copy link
Member

@aslakknutsen can you please look into this.

@kbsingh
Copy link
Collaborator Author

kbsingh commented Sep 20, 2017

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 ?

@alexeykazakov
Copy link
Member

@kbsingh yes, we are planning to address it. The corresponding issue on Auth side - fabric8-services/fabric8-auth#38

@joshuawilson
Copy link
Member

@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.

@alexeykazakov
Copy link
Member

@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.
The solution on our side would be to catch such errors (when OSO token is not good anymore) and initiate OSO account linking (see fabric8-services/fabric8-auth#38).

@RanjithRV
Copy link
Collaborator

@alexeykazakov curious regarding why we marked this issue as not a bug. This is not expected behaviour is it?

@alexeykazakov
Copy link
Member

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.

@qodfathr
Copy link
Collaborator

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.

@aslakknutsen
Copy link
Collaborator

aslakknutsen commented Jan 31, 2018

@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.. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants