Hi,
I am trying the IBM Verify Identity Access Extension for OIDC Provider Container, version 1.0.1, on the ISVA appliance version 10.0.8. The container image is "icr.io/ivia/ivia-oidc-provider:25.03". After created the container deployment with the REST API, I noticed the following error in the container logs:
951 2025-05-09T16:09:54.886881065-04:00 stdout F [05/09/2025 20:09:54.886 UTC] (internal.config.processKeystore) I [CORR_ID-6faabacd-affd-4fc6-887c-88179ba257ac] "Processing keystores"
952 2025-05-09T16:09:54.887026722-04:00 stdout F [05/09/2025 20:09:54.886 UTC] (internal.config.init) F [CORR_ID-6faabacd-affd-4fc6-887c-88179ba257ac] "Unable to continue. Error occurred when processing keystores: could not load keystore folder: open /var/isvaop/config/keystore: no such file or directory"
But the container metadata of the volume "configuration" has a different mount point:
"volumes": [
{
"name": "configuration",
"mountpoint": "/var/iviaop/config"
},
{
"name": "runjs_input",
"mountpoint": "/var/iviaop/input"
}
],
I am wondering why the newest version of oidc container is still looking for the path of "/var/isvaop/config/"? Did any body experience the same behavior?
Regards,
Eric
------------------------------
Regards,
Eric
------------------------------