Install/Run Instructions and SQLAlchemy Issue about pykmip

[joel-coffman]

I'll answer the easiest question:

What is the preferred way to run in version 0.4.1?

The PyKMIP server was added in version 0.5.0 (see CHANGES). Anything that existed prior to that time had very limited functionality -- essentially some sanity checks on the requests and responses for testing the client.

@PeterHamilton is the best person to address the rest of your questions.

[PeterHamilton]

Hi @kecalli, thanks for filing this issue. I've been out on vacation so I apologize for not getting to this sooner.

@joel-coffman is correct regarding version 0.4.1. Version 0.5.0 introduced a more mature server implementation that actually supports basic key management functionality; the 0.4.1 version (and prior) was really only good for sanity checks and networking tests.

Let's sanity check things first. Did you install PyKMIP 0.5.0 via pip or did you clone master from the GitHub repo and install that?

[kecalli]

Hi Peter,

No problem. Hope you enjoyed your vacation.

I have tried either the stable 0.5.0 release or cloning the master from
Github. In all cases, I installed using the "setup.py build/install"
process which I believe uses pip directly? It appears that I experience the
same results either way.

Thanks,

Keith

On Mon, Sep 26, 2016 at 12:30 PM, Peter Hamilton [email protected]
wrote:

Hi @kecalli https://github.com/kecalli, thanks for filing this issue.
I've been out on vacation so I apologize for not getting to this sooner.

@joel-coffman https://github.com/joel-coffman is correct regarding
version 0.4.1. Version 0.5.0 introduced a more mature server implementation
that actually supports basic key management functionality; the 0.4.1
version (and prior) was really only good for sanity checks and networking
tests.

Let's sanity check things first. Did you install PyKMIP 0.5.0 via pip or
did you clone master from the GitHub repo and install that?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#193 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVVUubScYLAzWaPZFCBa3-UavhZTU7TMks5qt_MIgaJpZM4KDy2f
.

[vvadimka]

Hi, Peter , just saw this topic and wanted to add that I am also getting the same error
I installed OpenKMIP release 0.5 and have a python 2.7 (latest version)
All certificates are installed and configured in the server and client configuration files

Getting the error from client when I tried to use as example:
c:\kmip\demos\pie>c:\Python27\python.exe create.py -a AES -l 256

2016-09-28 11:16:57,719 - kmip.server.session.00000001 - ERROR - 'NoneType' object has no attribute 'credential'
Traceback (most recent call last):
File "c:\Python27\lib\site-packages\pykmip-0.5.0-py2.7.egg\kmip\services\server\session.py", line 106, in _handle_message_loop
request
File "c:\Python27\lib\site-packages\pykmip-0.5.0-py2.7.egg\kmip\services\server\engine.py", line 142, in decorator
return function(self, _args, *_kwargs)
File "c:\Python27\lib\site-packages\pykmip-0.5.0-py2.7.egg\kmip\services\server\engine.py", line 252, in process_request
auth_credentials = header.authentication.credential
AttributeError: 'NoneType' object has no attribute 'credential'
2016-09-28 11:16:57,723 - kmip.server.session.00000001 - INFO - Stopping session: 00000001

I will very appreciate if you can maybe explain what does this error mean ?
Thanks,
Vadim

[PeterHamilton]

Unfortunately something's come up that has taken over my time. I'm planning on looking into this tomorrow/Friday. I haven't forgotten!

[PeterHamilton]

Ok, I'm running through some tests on this now. I suspect this is a bug on the server side, where it expects to see a credential coming from the client with the KMIP Create request. If I'm correct, a fix for this should be pretty easy. I'll post back once I've confirmed this.

[PeterHamilton]

I think I've identified the problem, but I'll need to confirm something with you both.

First: are you both using the PyKMIP client, or one of the client demo scripts in kmip/demos?
Second: if so, do you have username/password fields defined in your pykmip.conf file?

If the answer to #2 is no, the PyKMIP client will not send a credential with the server request, causing the error you're both seeing. The username/password fields can be empty in the pykmip.conf file, like so:

[client]
hostname=127.0.0.1
port=5696
...
username=
password=

It's a quirk of how the client currently works that's apparently not covered in our tests. Add those two lines to your pykmip.conf and things should work.

Regardless, the server should not generate an error on missing credentials (especially since they're not required). I'll post a server-side fix for this shortly.

[vvadimka]

Hi, Peter

Many thanks for your help. You are right , I used kmip/demos samples and user/passwords fields were missing
After I added them , the samples start working .
Again , thanks for your quick reply.

Thanks,
Vadim

[PeterHamilton]

Awesome, glad that was the right fix. Once I patch the client and server, this shouldn't be a problem again.

[PeterHamilton]

@kecalli - Going back to your first question regarding SQLAlchemy, that is a warning I've seen for a while now that I believe is related to a bug in how the Certificate object is mapped to the database. So far it hasn't produced any breaking behavior, so it hasn't been high on my fix list. I'll file a separate issue for it so that it can be tracked independently of this server bug.