GlaSSLess FIPS implementation#51082
Draft
slaskawi wants to merge 2 commits into
Draft
Conversation
This was referenced Jul 22, 2026
Signed-off-by: Sebastian Łaskawiec <sebastian.laskawiec@defenseunicorns.com>
Contributor
Author
|
@codex review |
slaskawi
marked this pull request as draft
July 23, 2026 07:24
Signed-off-by: Sebastian Łaskawiec <sebastian.laskawiec@defenseunicorns.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This Pull Request contains a prototype for introducing GlaSSLess FIPS provider into Keycloak codebase.
The
glassless_report.mdfile contains detailed information how GlaSSLess is integrated.How to play with it?
The easiest way to test this out is to use a pre-built Docker container and foloowing the guide below.
1. Pull the image
2. Start Keycloak
The bootstrap password below is deliberately long enough for strict FIPS mode.
The image is already optimized with these FIPS settings. Supplying them explicitly at startup makes the selected mode and provider visible and verifies that the invocation matches the optimized image.
3. Wait for readiness
docker logs --follow "$CONTAINER_ID"The important messages are:
Press
Ctrl+Cafter the startup message. Then verify OpenID discovery:curl --fail --silent --output /dev/null --write-out 'HTTP %{http_code}\n' \ http://127.0.0.1:8080/realms/master/.well-known/openid-configurationExpected result:
The administration console is available at http://127.0.0.1:8080/admin/ using
adminandglasslessAdminPassword25.4. Request a token
curl --fail --silent \ --request POST \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data client_id=admin-cli \ --data username=admin \ --data password=glasslessAdminPassword25 \ --data grant_type=password \ http://127.0.0.1:8080/realms/master/protocol/openid-connect/tokenA successful response contains a three segment JWT
access_tokenand"token_type":"Bearer".5. Verify Glassless and OpenSSL FIPS status
Expected result:
Verify the persisted Keycloak provider selection:
Expected configuration includes: