Unable to configure kmip client

Vault
21

I did, but that was before I was passing the correct name, in my comment earlier, I shared this snippet

| | Tag: ResponsePayload
| | Type: Structure
| | Length/Padding: 56/0
| | | Tag: ObjectType
| | | Type: Enumeration
| | | Length/Padding: 4/4
| | | Value: 7
| | | Tag: UniqueIdentifier
| | | Type: TextString
| | | Length/Padding: 32/0
| | | Value: 9DzPQoQv8wntpaPu9XsAFlh3TvydVupz

So we can see that the uid has been returned and it’s valid as well, I can get the value I stored via this but the ObjectType tag being returned is not expected by pykmip and to the best of my knowledge neither does the spec which is what I was asking.

Please let me know if I should elaborate. Thanks

22

Ah, sorry I was the one missing something. I agree, it doesn’t look like ObjectType should be there. Yes, please file a github issue.

23

Great, I’ll do that. Thank you

24

@sonicaj Could you please give details on the tweak that you did? I am facing the same problem, but could not workaround it.

25

Although you have not provided the server’s response header to your KMIP v1.4 request, by virtue of having received an intelligible response you can rest assured that the server understands (at least) KMIP v1.4.
You might also employ KMIP’s Discover Versions operation.