Toni

I ran into this same issue. I created a new realm manually, and then attempted to add RSA keys using keycloak_realm_keystore_rsa. No errors, Terraform's plan and apply looks good, but...

Hi, would you create a pull request? I will then merge and release it. Thanks!

Sorry, I can't do much without having a possibility to use the remote controller. All the work is based on reverse-engineering, by using software like this: https://github.com/ToniA/Raw-IR-decoder-for-Arduino

Hi, sorry for not responding earlier. So this 'I-Feel' is a special command (temperature measurement) sent periodically by the remote controller? This would need a protocol decoding from a real...

Also, it would't hurt if 'JFrog CLI V2' would support 'workingDirectory', for example for running 'jf audit-npm' in a subdirectory.

@gim- Any chance you could publish your build into Terraform registry? _Just banging my head against the wall with this priority mess..._

I got somewhere with raw REST API, using magodo/restful ``` terraform { required_providers { keycloak = { source = "mrparkers/keycloak" version = "=4.4.0" } restful = { source = "magodo/restful"...

A really ugly way to add the IdP into an organization. No error checking or anything, but it does the trick ``` data "http" "keycloak_token" { url = "http://localhost:8000/realms/master/protocol/openid-connect/token" method...

This is probably a bug. @geonux?

You're probably right on this one... Would you create a pull request with the fix (and please verify that it's also working correctly on non-inverted case)?