lorandt1

@michalvasko taking into account that algorithm leaf of type identityref used in o-ran-file-management but imported from ietf-crypto-types defined as follows: ``` ``` ``` grouping public-key-grouping { description "A public key....

Hi, @michalvasko I will attach the used yang files to make it clear. As you confirmed earlier > Yes, identity names (identityref values) should always be [fully qualified](https://www.rfc-editor.org/rfc/rfc7950.html#section-9.10.3), must be...

` application operation-failed error\ Unexpected valid opaque node list "keys". application operation-failed error RPC input validation failed. `

@michalvasko thank you so much!

Hi @michalvasko, thanks for your reply! Indeed I don't use the modules provided by libnetconf2 but other ones with different revisions. **So I will check with the yang modules using...

Could you please let me know what is wrong in **ietf-keystore.yang** and **ietf-ssh-server.yang** that leads to those **ly ERR** [yang_2.tar.gz](https://github.com/CESNET/libyang/files/15249698/yang_2.tar.gz) - are those valid errors based on RFC ? if...

Hi, I have to reopen the issue as I encounter the same issue with other server.. `- ly ERR: Invalid identityref "ct:rsa2048" value - identity found in non-implemented module "ietf-crypto-types".(/o-ran-file-management:file-upload/server/keys/algorithm)`...

I am using libnetconf2 v3.0.17. I encounter all these issues during the upgrade from 2.0.24. Why it looks like an old version is used ? I will try to add...

Hi @michalvasko It indeed seems to be due to version of ietf-crypto-types.yang as it still appears also without those modules that couldn't be loaded. I must keep ietf-crypto-types.yang at revision...

I don't need multiple revisions, only one, which is older than libnetconf2 provides by default for ietf-crypto-types: 2019-04-29. Could libnetconf2 support that version too and avoid that issue that I...