Skip to content
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

fix(jans-fido2): Contents of authenticatorCertsFolder from fido2 configuration are not being loaded #10610

Closed
maduvena opened this issue Jan 13, 2025 · 2 comments
Assignees
Labels
comp-jans-fido2 Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Milestone

Comments

@maduvena
Copy link
Contributor

Reference issue #9369

Contents of authenticatorCertsFolder from fido2 configuration are not being loaded

  "fido2Configuration": {
        "authenticatorCertsFolder": "/etc/jans/conf/fido2/authenticator_cert",

Check : AttestationCertificateService.java and init method.

@mo-auto mo-auto added comp-jans-fido2 Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality labels Jan 13, 2025
@shekhar16
Copy link
Contributor

@devrimyatar Regarding authenticator_cert folder present in property authenticatorCertsFolder , we have to download these files inside DB instead of folder as same as we have done for mdsTocsFolder and mdsCertsFolder in ticket #9610

please check below code for authenticator_cert.
https://github.com/JanssenProject/jans/blob/main/jans-linux-setup/jans_setup/setup_app/installers/fido.py#L92

@moabu moabu added this to the next-release milestone Jan 21, 2025
@imran-ishaq
Copy link
Contributor

The investigation revealed that the certificates weren't being saved in the database. This caused the loading to fail. After modifying the fido.py script to store the certificates in the database, the content loaded successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-jans-fido2 Component affected by issue or PR kind-bug Issue or PR is a bug in existing functionality
Projects
None yet
Development

No branches or pull requests

5 participants