User Security

8 views
Skip to first unread message

David

unread,
Dec 23, 2017, 1:08:33 AM12/23/17
to pytomation
I committed the first part of the user security piece, in the "user" branch, which is based of the "python3" branch. Currently, it only allows you to restrict a user to certain devices; but the infrastructure is built, so it won't be much to add the command level security now.

I have an example on how to use in the dopeyrealm instance. It's usage will change as the command security is added, however.

Note that the plain HTTP server isn't working right now. I got it mostly working, but it fails some tests, so I have it disabled. I'm not sure if it's really needed anymore though, so I may not spend more time trying to get it working. The PytoWebSocketServer works much better and gives continuous updates, via the web-socket.

George Farris

unread,
Dec 26, 2017, 5:11:45 PM12/26/17
to pytom...@googlegroups.com
Our last visitors are leaving today so hope to start some testing on the python 3 port soon.

George
--
You received this message because you are subscribed to the Google Groups "pytomation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pytomation+...@googlegroups.com.
To post to this group, send email to pytom...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jason Sharpee

unread,
Dec 26, 2017, 6:07:35 PM12/26/17
to pytom...@googlegroups.com
Awesome!

By all means if no one is using the simple http server delete it.

--
You received this message because you are subscribed to the Google Groups "pytomation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pytomation+unsubscribe@googlegroups.com.

David

unread,
Jan 2, 2018, 2:35:24 AM1/2/18
to pytomation
I actually got the HTTPSever interface working again. I figured there was still a use case for using the fewer resources required with this type of server. Pytomation would just be without the websockets and SSL.

The old one, in utility, I removed, however.

This user update actually wasn't what broke it, the Python SimpleHTTPHandler class was updated and required a couple calls to be changed. It could have happened during the Python 3 update, but I honestly haven't modified, used, or tested that simple HTTP server in a long time, so I'm not really sure.


On Tuesday, December 26, 2017 at 3:07:35 PM UTC-8, Jason wrote:
Awesome!

By all means if no one is using the simple http server delete it.
On Dec 23, 2017 1:08 AM, "David" <king.dop...@gmail.com> wrote:
I committed the first part of the user security piece, in the "user" branch, which is based of the "python3" branch. Currently, it only allows you to restrict a user to certain devices; but the infrastructure is built, so it won't be much to add the command level security now.

I have an example on how to use in the dopeyrealm instance. It's usage will change as the command security is added, however.

Note that the plain HTTP server isn't working right now. I got it mostly working, but it fails some tests, so I have it disabled. I'm not sure if it's really needed anymore though, so I may not spend more time trying to get it working. The PytoWebSocketServer works much better and gives continuous updates, via the web-socket.

--
You received this message because you are subscribed to the Google Groups "pytomation" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pytomation+...@googlegroups.com.

David

unread,
Jan 14, 2018, 2:01:05 AM1/14/18
to pytomation
I added the device command security to the feature\users repo and will soon be merging that to dev. An example usage is in the dopeyrealm instance. The syntax didn't change much. The only change is if you want to restrict a device commands, instead of just adding the device to the accessible_devices parameter, you add a tuple that contains the device and a list of commands.
Reply all
Reply to author
Forward
0 new messages