Add exporting individual attributes and a map endpoint #26
Labels
No labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Depends on
#25 Fix matchRole lookup to include group-inherited and composite roles
CCCHH/keycloak-attribute-endpoints-provider
Reference
CCCHH/keycloak-attribute-endpoints-provider!26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "add-map-endpoint"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Based off #32
Also:
Closes #22
Haven't tested the PR yet, but it looks reasonable so far.
@ -146,0 +83,4 @@* @return*/@GET@Path("export/{attributeGroupName}/map")why is the
slugnamedattributeGroupNamein this path? As far as I can see, it has no connection to the actual attribute group name and can still be chosen freely.@stb
Since @june and I have put a lot of time and energy into this project and I’d like to continue standing behind the codebase, I’d like to ask you to clarify whether the code was modified by an AI Agent or if you refactored it by hand.
It's done by hand, but it's not correct. Give me some time to wrap my head around everything.
Add an endpoint producing the individual attribute values per nameto WIP: Add an endpoint producing the individual attribute values per nameWIP: Add an endpoint producing the individual attribute values per nameto Refactor and expandstb referenced this pull request2026-07-18 20:00:40 +02:00
@ -20,79 +42,8 @@ Once all dependencies are met, simply call `make` to build the provider, which sThere's also `make clean` available for removing the output directory.To add the provider to your Keycloak install, copy `attribute-endpoints-provider/target/attribute-endpoints-provider-1.0-SNAPSHOT.jar` to the Keycloak Provider directory (`/opt/keycloak/providers/).missing backtick:
Is it possible to split this PR into seperate PRs? It's too confusing for me to compare the large diff and a review commit by commit is also not possible, as some thing are reverted by a following commit.
I propose:
Does this work for you @stb?
I can also try wrapping my head around this and split the PR, but I don't think I will have time for that in the neear future :/
Hhm, splitting this up is a lot of additional work, and it risks introducing additional unwanted changes in the process. Let me think about what it would take to split it up like that.
CAn you at least try and run it as is and tell me whether the tests and the docker compose integration testing are working for you?
@stb wrote in #26 (comment):
Yes, will try to test the PR tomorrow
I've created #31 for the testing infrastructure, and #32 for the refactoring. After merging those, this can be rebased for an easier review. I can split out the doc changes, but I think it's easy enough to do those as part of this.
6ef6d7adebc9f36f7100Refactor and expandto Add exporting individual attributesAdd exporting individual attributesto Add exporting individual attributes and a map endpointI've rebased this PR off #32. I hope the three PRs together make the changes clearer.
If people are happy with everything, merging #31 and #32 can be skipped, since this includes all changes.
c9f36f7100af1a869de9@ -4,2 +3,2 @@For this it will provide API endpoints for every configured attribute-group.The configuration of the provider is possible via an admin page.This is a Keycloak Provider that exports user profile attribute values.The selection of attributes and authorization is manage through an endpoint configuration."The selection of attributes and authorization is managed through an endpoint configuration via the admin UI."
@ -122,2 +128,4 @@.add().property().name("attribute-group")Let's have a comment here to note that we leave this name for backwards compatibility.
Looks good!