OIDC: Support using PKCS12 keystores for creating signed JWT tokens

[michalvavrik]

• Closes: OIDC can only use JKS keystores for creating signed JWT tokens #43176

This differs from #43176 description slightly in a fact that we assume JKS if the keystore file extension is not recognized. But that is only because I want to keep current behavior and use one method inside OIDC. IMHO we need to be consistent inside OIDC.

quarkus/extensions/oidc-common/runtime/src/main/java/io/quarkus/oidc/common/runtime/OidcCommonUtils.java

Line 219 in e878841

// assume jks

Also, this makes this PR backwards compatible.

[github-actions]

🙈 The PR is closed and the preview is expired.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit bf81d72.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit bf81d72.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[sberyozkin]

Thanks @michalvavrik

[sberyozkin]

Usually it is a p12 extension, but having an expanded name to test is good