-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFE] Continue searching other PKCS#11 tokens if certificates are not found #5905
Comments
(splitted of #5025) |
Hi! We faced with the same problem. I got that you have a lack of time to implement this. If we implement it for you, this MR will be had a chance to be merged? We can implement retrieving all certs on all tokens, and suggest user to choose a label of a proper one. Would it be ok for you? |
Hi, it would be very welcome if you can provide a patch to iterate over all slots and tokens. Please note that SSSD can already handle multiple certificates and prompt the user if more than one pass mapping and matching rules. So you only have to add the iteration. Thanks. bye, |
Will do later lol Resolves: SSSD#5905
Explanation: Will do later lol Resolves: SSSD#5905
Explanation: Will do later lol Resolves: SSSD#5905
p11_child
handles (pre-)authentication in two steps. In the first step, it locates a PKCS#11 token that could contain certificates for authentication. In the second step, it checks if there are actually valid, usable certificate(s) on it.During both steps, filtering is performed based on arguments given to
p11_child
. If a mismatch occurs during the first step, it simply skips the module/slot/token and goes onto the next one. However if a mismatch occurs in the second step, this is considered a failure; it does not return to the first step to see if a different token contains the right certificates (or to wait for it, if--wait_for_card
is given).To address this, the code needs to be refactored so that the certificate search happens inside the loop that searches/waits for tokens.
The text was updated successfully, but these errors were encountered: