Expose token entity/job info through BfabricUser#485
Merged
leoschwarz merged 3 commits intomainfrom Apr 15, 2026
Merged
Conversation
When B-Fabric launches a webapp via token, TokenData contains rich context (entity_class, entity_id, job_id, application_id) that was previously lost after token validation. This makes the info accessible directly via BfabricUser properties, removing the need to use the on_success hook to capture it. - Add optional token context fields to SessionData - Populate them from TokenData in middleware _handle_landing() - Add corresponding properties on BfabricUser - Add unit tests and BDD scenarios for the new fields
These fields are always present when created from a token, so there's no reason to make them optional. This is a breaking change for any code constructing SessionData without them.
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
1 participant
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.
entity_class,entity_id,job_id, andapplication_idas optional fields onSessionDataand read-only properties onBfabricUserTokenDataduring token validation, so app code can useuser.entity_classanduser.entity_iddirectlyon_successhook