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
User cannot update profile when some invalid attribute invisible to him is present on his profile #24697
Closed
1 task done
Tracked by
#23905
Comments
14 tasks
rmartinc
added a commit
to rmartinc/keycloak
that referenced
this issue
Nov 13, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
pedroigor
pushed a commit
that referenced
this issue
Nov 14, 2023
…ng and read-only in the context Closes #24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
sschu
pushed a commit
to bosch-io/keycloak
that referenced
this issue
Nov 15, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
Yang-Xie-OSS
pushed a commit
to Hitachi/keycloak
that referenced
this issue
Nov 21, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
jonkoops
pushed a commit
to jonkoops/keycloak
that referenced
this issue
Nov 21, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
Yang-Xie-OSS
pushed a commit
to Hitachi/keycloak
that referenced
this issue
Nov 22, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
jonkoops
pushed a commit
to jonkoops/keycloak
that referenced
this issue
Nov 22, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
srose
pushed a commit
to srose/keycloak
that referenced
this issue
Dec 20, 2023
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com>
kamontat
pushed a commit
to kamontat/keycloak
that referenced
this issue
Jan 20, 2024
…ng and read-only in the context Closes keycloak#24697 Signed-off-by: rmartinc <rmartinc@redhat.com> Signed-off-by: Kamontat Chantrachirathumrong <14089557+kamontat@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before reporting an issue
Area
user-profile
Describe the bug
User cannot update his profile (in "Update profile" required action or in account console) when there is some attribute, which is hidden to him (according to user-profile definition) and which has invalid value according to user-profile validation.
User should not be stucked because attribute is invisible to him and hence he should be allowed to proceed as he cannot update the attribute
Version
nightly
Expected behavior
Allow user to continue login (or update his account in account console) when there is some invisible attribute on him with invalid value (invalid value according to user profile validations)
Actual behavior
User is stucked when updating profile when there is some invisible attribute on him with invalid value (invalid value according to user profile validations)
How to Reproduce?
john
with passwordjohn
foo
with valueabc
Update profile
to userjohn
foo
with length to be between 5 and 15 characters (So attributefoo
on userjohn
is invalid now according to this defined validation). Make sure that attribute is visible and editable only for administratorjohn
. User needs to update his profile. Attributefoo
is not shown on the update-profile screen, which is correct.foo
on userjohn
to have valid value likeabcdef
.User is not able to update his attributes in account console as well when he has invalid value of some attribute, which is not visible to him.
So it is clear that the issue is caused by the fact that user
john
has invalid value of attributefoo
on his profile. However since it is not attribute editable for him, and he did not updated it in this request, he should be allowed to login.Anything else?
No response
The text was updated successfully, but these errors were encountered: