fix: SendAuthResultToUDM#51
Merged
Merged
Conversation
Contributor
Author
|
@Alonza0314 |
Alonza0314
approved these changes
Feb 6, 2026
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
2 participants
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.
What bug it fixes
SendAuthResultToUDM should identify the UE using the SUPI so that UDM can correctly associate and store/process the authentication result for the right subscriber.
Using eapSessionID (a session identifier) instead of currentSupi could cause:
UDM not being able to find the correct UE/subscriber record
the authentication result update failing or being applied incorrectly
This PR ensures that when EAP-AKA' authentication fails, AUSF reports the result to UDM using the correct UE identity (currentSupi).