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

Mappers tab is not reachable on identity provider settings #20782

Closed
2 tasks done
onikitin-iqmessenger opened this issue Jun 5, 2023 · 3 comments · Fixed by #20813
Closed
2 tasks done

Mappers tab is not reachable on identity provider settings #20782

onikitin-iqmessenger opened this issue Jun 5, 2023 · 3 comments · Fixed by #20813
Assignees
Labels
Milestone

Comments

@onikitin-iqmessenger
Copy link

Before reporting an issue

  • I have searched existing issues
  • I have reproduced the issue with the latest release

Area

admin/ui

Describe the bug

There is no possibility to reach the Mappers tab after the creation of the SAML v2.0 identity provider in case you add spaces in the alias field.

Version

21.1.1

Expected behavior

There is validation on the alias field on the step of the creation of the identity provider to prevent the incorrect working of that in the future.
OR
The alias field value is trimmed before saving.
But preferably there to be validation, to prevent saving with spaces or other forbidden symbols.

Actual behavior

The form is saved without any constraints about the spaces so it does not allow user to set up any mappers

How to Reproduce?

  1. go to Identity providers
  2. click Add provider → SAML 2.0
  3. set up any provider with the space in the Alias field
  4. save the provider

Anything else?

No response

@ssilvert
Copy link
Contributor

ssilvert commented Jun 5, 2023

I have reproduced this. Permissions tab is also not reachable.

@edewit
Copy link
Contributor

edewit commented Jun 6, 2023

Should we make it invalid to put an space?

edewit added a commit to edewit/keycloak that referenced this issue Jun 6, 2023
edewit added a commit that referenced this issue Jun 12, 2023
@onikitin-iqmessenger
Copy link
Author

hello @edewit!
will this fix be ported to 21.1.x?

@jonkoops jonkoops added this to the 21.1.3 milestone Jun 22, 2023
srose pushed a commit to srose/keycloak that referenced this issue Jun 26, 2023
@jonkoops jonkoops modified the milestones: 21.1.3, 22.0.0 Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants