Search the Community
Showing results for tags 'authentication'.
Found 2 results
Hello LV Gurus, I am creating a simple GUI to control a web (specifically RESTful web server) based DLI Web Power Switch Pro I have three problems: What is the "Base URL" Is it just the IP + port (e.g. http://192.168.0.100:80) or the whole URI including the path to the web server (e.g. http://192.168.0.100/restapi/relay/outlets/0/state/) Where and how do I insert the cross-site forgery ignore in the header (e.g. X-CSRF:x) with your REST API? The Default Header list does not include X-CSRF. Do you support Basic and/or Digest authentication? I get "Unauthorized" error messages using your PUT (or GET) methods returned in the Status String. I then proceeded to create a version of this GUI using cURL (via the System Exec node) to enable switch outlet 1 using "digest" authentication and it works: curl --digest -u admin:1234 -X PUT -H "X-CSRF: x" --data "value=true" "http://192.168.0.100/restapi/relay/outlets/0/state/" FYI: This is DLI guideline for using RESTful HTTP on their power switches Thanks in advance guys. You do wonders for us LabVIEW cogs! Relativity1
Hi, I have set up an internal VIP repository on a server and expose that to my users with Apache webserver using HTTPS. It works fine and after the users authenticate themselves with username and password they can see and download the packages in the repo. The problem is that even though they click "Use Password Manager to remember this password" they still get the authentication dialog the next time they open VIPM, and without any pre-filled data. Really annoying. Is there anything I must do on the web server to make it work or is this a bug? I'm using VIPM 2014.0.0 build 1941. The Apache version is 2.2.15 with a SSL-certificate issued by COMODO CA Limited. Kind regards LeifS