Closed PauAL closed 1 year ago
Thanks for raising this issue. I installed exact same version on my OpenShift cluster but I'm not able to reproduce it at the moment.
From what I understand, you're facing same issue with both Keycloak coming with Microcks and external Keycloak. Is that correct?
Are you cluster nodes running with some special constraints as the OS/System level? (thinking about SCC, SELinux profiles, seccomp profiles, FIPS enforcement or whatever....)
Also have you check the algorithm that are referenced when calling /realms/microcks/protocol/openid-connect/certs
on you Keycloak server? On mine I just have RSA-OAEP
and RS256
. No Sha1 with RSA...
Yes, I am facing the same issue with Microcks and with an external keycloak.
I would say we do not have any special security constraint as we where able to connect different apps to our keycloak already, but I will check it in the meantime just in case.
The certs algorithms are RSA-OAEP and RS256 (default certs configured in Microcks keycloak). I also do not know where this SHA1withRSA is coming from.
Regards.
Too bad... Don't know how to get with this one, as I never faced this one... Looking for some Keycloak friends around... Maybe @M3lkior this would be something you're aware of?
hey ; nop; unfortunatelly ; maybe this is not a Keycloak issue.
you can maybe play with your key length that is maybe the root cause of your problem regarding this kind of post: https://stackoverflow.com/questions/21218217/ssl-handshake-exception-algorithm-constraints-check-failed-md5withrsa
Hi, M3lkior, thank you for your comment. Unfortunately, I already checked and our key complies with the 1024+ bits long restriction so it should not be the problem.
I would appreciate any additional ideas to make this work.
Regards.
Well, trying to figure it out I started reducing failure points. I configured in the operator keycloaks private URL to avoid the certification validation and it worked. Even when the certificate complies with the restriction there is something avoiding the connection.
Anyway, I would close this issue cause is seems it is not an operator problem, if you agree.
Describe the bug
We installed microcks using microcks-ansible-operator (1.7.0 version, Build timestamp 2023-03-08T15:54:54Z) on openshift using this configuration:
Installation worked and after successfully uploading a dummy artifact we were not able to see it in "APIs | Services" page. I checked and saw some 500 errors, all of them where from request to “/api/jobs/*” endpoints. In my-microcksinstall logs I could see the following trace:
It seems keycloak adapter is giving a NPE cause it is not able to retrieve any of the public certs published under “/protocol/openid-connect/certs”. This seems caused by the warning
Caused by: java.security.cert.CertPathValidatorException: Algorithm constraints check failed on signature algorithm: SHA1withRSA
.Previous to this installation we installed microcks connected with our keycloak server. We got this error and checked again with operator installed keycloak just to check if it was caused by out keycloak configuration.
Expected behavior
No errors are expected.
Actual behavior
I receive a 500
{"timestamp":1681466461351,"status":500,"error":"Internal Server Error","path":"/api/jobs/count"}
at every "/api/jobs". This error is blocking me to operate microks, I cannot see any of the APIs or services published.How to Reproduce?
To reproduce this behaviour:
Microcks version or git rev
1.7.0 version, Build timestamp 2023-03-08T15:54:54Z
Install method (
docker-compose
,helm chart
,operator
,docker-desktop extension
,...)microcks-ansible-operator
Additional information
No response