Has anybody experience in this?
I just saw your thread. I may not be fully up to speed to what is going on here, but let me try to help. I see that you are using a jama-csrf token from the cookies. You should not need this to authenticate via REST API. in order to authenticate to the rest api basic authentication you can do the following:
Most rest clients have an easy interface for basic authentication. You must provide your username and password in the header of the request following the RFC 2617 standard
Note: This type of authentication will not work in a SAML/SSO environment.
Examples for username: "myusername" and password: "mypassword"
HeaderAuthorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3JkName: "Authorization", value: "Basic AUTHORIZATION", where AUTHORIZATION is a Base64-encoded presentation of "myusername:mypassword"
Authorization: Basic bXl1c2VybmFtZTpteXBhc3N3b3Jk
Curl Examplecurl -u myusername:mypassword http://basepath/rest/v1/projectsBest Regards,
curl -u myusername:mypassword http://basepath/rest/v1/projects
So, I got a response from the server and made it through the three gates of security to establish contact.
1) The user name and password in open handle do nothing for the JAMA authentication.
2) I had to make a custom header "Authorization" with the value "Basic <username>:<password>"
3) My server is setup for SSL, and I only had to create a certificate for the CA certificate file input. This was done in chrome by clicking on the lock icon in the address bar, and exporting a 64 bit cer file.
4) Verify Server is set to false. Setting it to true will generate an error on the GET command.
5) I needed a cookie file so that the jama-csrf-token could be generated
I hope this helps anyone else who may have to interface with JAMA with LabVIEW. The LabVIEW snippet is located in this forum on the NI website.https://forums.ni.com/t5/LabVIEW/JAMA-amp-the-RESTful-interface/m-p/4174212#M1206357
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204