[autobackport: sssd-2-11] krb5_child: use ERR_CHECK_NEXT_AUTH_TYPE instead of EAGAIN #8230
+31
−23
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.
This is an automatic backport of PR#8176 krb5_child: use ERR_CHECK_NEXT_AUTH_TYPE instead of EAGAIN to branch sssd-2-11, created by @sumit-bose.
Please make sure this backport is correct.
Note
The commits were cherry-picked without conflicts.
You can push changes to this pull request
Original commits
7ddb51f - utils: add new error code ERR_CHECK_NEXT_AUTH_TYPE
0adc2e7 - krb5_child: use ERR_CHECK_NEXT_AUTH_TYPE instead of EAGAIN
da82d1d - krb5_child: clarify EAGAIN returned by krb5_get_init_creds_password()
Backported commits
Original Pull Request Body
This patch used the new error code ERR_CHECK_NEXT_AUTH_TYPE while
processing different authentication types instead of EAGAIN because
EAGAIN might have side effects when returned to the callers.
Resolves: #8108