Hafid Haddouti

I tried the latest version from master ``` git clone https://github.com/Apicurio/apicurio-studio cd apicurio-studio/distro/openshift oc create -f apicurio-standalone-template.yml oc process apicurio-studio-standalone | oc create -f - ``` api-component is not starting...

[apicurio-studio-api.log](https://github.com/Apicurio/apicurio-studio/files/7448480/apicurio-studio-api.log)

@lbroudoux good point with the dev console. The first issue was a 401, cause I added in the `MicrocksInstall` `privateURL` field the k8s internal URL to Keycloak. After switching to...

one of the main problem is the old keycloak version in the Apicurio Auth, 4.1.0.Final. otherwise the import of the config files would work Do you know how to update...

no, I stopped the manual adjustments into the Keyloak of Apicurio, due the fact, that both versions are different and not all elements/fields are visible/same - for me is not...

nice point with the Operator! And also nice, if you could provide any details, I am happy to validate in my environments! :-)

@Didainius yes, see enclosed the resource definition. ``` # Create a VM, bastion 0 resource "vcd_vapp_vm" "okd_bastion_vm00" { name = "okd_bastion_vm00" vapp_name = vcd_vapp.okd-bastion-vapp.name template_name = "CentOS-8-Template-Official" power_on = "true"...

probably an other case * BOM generated * afterwards validate and the generated BOM is not valid, without any modification ``` /cyclonedx add files --no-input --output-format json --output-file sbom.json --exclude...

without `generic` detector simple `password` fields in prop files will be not detected. I would recommend that we can enable this detector too. Probably with an additional flag, which enable...

@SecTheBit yes correct, but without using it, you miss also all the clear problematic fields. This is the reason, why requesting this as optional detector and the caller/user has the...