Skip to content
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

OAUTH Authenticated users not shown correctly #686

Closed
imagdy83 opened this issue Mar 5, 2024 · 10 comments
Closed

OAUTH Authenticated users not shown correctly #686

imagdy83 opened this issue Mar 5, 2024 · 10 comments
Assignees

Comments

@imagdy83
Copy link

imagdy83 commented Mar 5, 2024

when a user logs in via oauth, the username is displayed as jiberish as shown in the image attached
Username should be mapped correctly
image

@balaji-jr balaji-jr assigned balaji-jr and unassigned balaji-jr Mar 5, 2024
@nitisht nitisht added this to the Release v0.9.1 milestone Mar 5, 2024
@imagdy83
Copy link
Author

imagdy83 commented Mar 7, 2024

any updates?

@nitisht
Copy link
Member

nitisht commented Mar 7, 2024

We'll try to fix this in the next release

@nitisht
Copy link
Member

nitisht commented Apr 6, 2024

Fixed by #742

@nitisht nitisht closed this as completed Apr 6, 2024
@imagdy83
Copy link
Author

imagdy83 commented Apr 9, 2024

@nitisht issue has not been resolved, and it is unrelated to keycloak

@imagdy83
Copy link
Author

imagdy83 commented Apr 9, 2024

when a user logs in via oauth, the username is displayed as jiberish as shown in the image attached Username should be mapped correctly image

@nitisht users are still displayed as gibberish

@nitisht
Copy link
Member

nitisht commented Apr 9, 2024

What is the version you're running? We've not yet made the release.

@imagdy83
Copy link
Author

imagdy83 commented Apr 9, 2024

If the release wasn't made why was this issue closed and marked as solved by the latest release? 🤨
I'm running on the latest release 0.9.0

@nitisht
Copy link
Member

nitisht commented Apr 9, 2024

Fixed by #742

This is the comment. It doesn't say latest release, it is implied that it will be available when new release is made. What are you expecting?

@imagdy83
Copy link
Author

imagdy83 commented Apr 9, 2024

#638
My issue is not linked to keycloak and the issue was closed, I expect the issue to be closed with the problem fixed which is not the case.

@nitisht
Copy link
Member

nitisht commented Apr 9, 2024

I expect the issue to be closed with the problem fixed which is not the case.

Issue is closed because it is fixed in main. It will be available when we make the next release. Hope this clarifies. Thank you for the patience.

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

No branches or pull requests

3 participants