New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[management] Reference data identifying a user is not consistent accross management API cluster #1133

Closed
fabMrc opened this Issue Mar 7, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@fabMrc

fabMrc commented Mar 7, 2018

Hi

Behind a Proxy , 2 api node
When I get a user with /search/users?q=myuser I get a json structure composed of

  • id
  • reference
  • displayName

Because id is not always present (for exemple with default admin user) I use reference to identify my user in next actions

Now I want to transfer ownership using rest api
the endpoint response HTTP 404 user not found randomly

In a basic context with only one api node I have not such error, If a use user ID I have not error

Seems clustering context generate some issue using user with reference

@aelamrani aelamrani changed the title from Reference data identifying a user is not consistent accross API cluster to [management] Reference data identifying a user is not consistent accross management API cluster Mar 7, 2018

@aelamrani aelamrani added the type: bug label Mar 7, 2018

aelamrani added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Mar 7, 2018

@aelamrani aelamrani self-assigned this Mar 7, 2018

@fabMrc

This comment has been minimized.

fabMrc commented Mar 20, 2018

Any news about a release date that could embed this fix ?

@NicolasGeraud

This comment has been minimized.

Member

NicolasGeraud commented Mar 20, 2018

tomorrow if everything's ok.

aelamrani added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Mar 21, 2018

NicolasGeraud added a commit to gravitee-io/gravitee-management-rest-api that referenced this issue Mar 21, 2018

@NicolasGeraud NicolasGeraud added this to the 1.14.3 milestone Mar 21, 2018

@fabMrc

This comment has been minimized.

fabMrc commented Mar 26, 2018

Before Reopen a new issue I would just to be sure the bug is not fixed. With the 1.14.3 my admin local user with no ID but a reference ID works whereas it was not working before.
Now when a want to transfer ownership to a SSO user (hosted in a Keycloak) using the Reference ID it fails. The user is not found.
Please keep me in touch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment