API without password

Discussions about RaZberry - Z-Wave board for Raspberry computer
Post Reply
qbawawa
Posts: 27
Joined: 30 Oct 2015 18:58

API without password

Post by qbawawa »

Hi,

when I try to reach API from raspberry-pi (localhost) I get message Forbidden (as I understand this is problem with authorization), but when I try to run it from other computer in network it works fine.

How to setup it to not require authorization from localhost and require from other sources?

Regards!
AlphaX2
Posts: 110
Joined: 25 Jul 2015 15:03

Re: API without password

Post by AlphaX2 »

Maybe you were logged in already (web ui?) with this other computer. But it should work to create a "Anonymus" user, without a password for accessing the API without authentification, but this would also work from "outside" for both port forwarding and zbox solution, as far as I know. Don't know if it's also working with a password less "local user"?!
qbawawa
Posts: 27
Joined: 30 Oct 2015 18:58

Re: API without password

Post by qbawawa »

I'm not logged to web ui. Also - I create "Anonymous" user without password, but still when I try to make http request from localhost I get response "Permission denied".
SkjeggPT
Posts: 8
Joined: 10 Dec 2015 00:09

Re: API without password

Post by SkjeggPT »

when trying to make an anonymous user, name, login and password are mandatory..
is there any way to disable authentication on local network or just disable all together..

Or is buying a vera or HC2 the only way to go?
noah
Posts: 3
Joined: 31 Mar 2015 11:19

Re: API without password

Post by noah »

same question here, is there a solution for access in the local network without logging in.
bogr
Posts: 190
Joined: 16 Nov 2015 22:46

Re: API without password

Post by bogr »

There's another thread about this. As I understand it the solution at the moment is to create a separate "room" and make it available for the anonymous user. Then add the devices etc to that room. I don't think that's the "ultimate" solution, but it works. Another, more complex but "better" in my opinion, is to set up a webserver (e.g. nginx) that handles the authentication and just forward the calls to z-way.
Post Reply