Authorization Header Question/Problem

When use the header Authorization: BASIC alex_millen@westtool.com:mypassword I get back a 200 with the content "Login error. Please try again.Invalid password." (base64 encoded) If I base64 encode the string "alex_millen@westtool.com:mypassword" and use that after BASIC, I get back a 200 with the content "Login error. Please try again.Login error : Invalid userId or password.java.lang.Exception: Login error : User not authorized." (base64 encoded) What am I doing wrong? Alex Millen alex_millen@westtool.com 971-236-0409

Comments

  •  
    Can I get an update on this issue?
    Posted by Hidden Tue, 25 Sep 2018 21:13:22 GMT
  •  
    Alex, The login information is not your portal login. you would need a WIDIACenter login credential here. The format you used at the first go is correct but please use it with the WIDIACenter username and password. Let me know if it works. Also, please contact me on my direct email vijay.jayaram@kennametal.com
    Posted by Hidden Wed, 26 Sep 2018 15:30:27 GMT
  •  
    That worked, thank you.
    Posted by Hidden Wed, 26 Sep 2018 18:24:26 GMT
  •  
    The below javascript is from the example page which shows a section for params. I presume that I would put in there username/password. I then put in my key (replaced with X's). Login service does not require any input in the body section of the message so I left it blank.. I then get this response.. {statusCode: 401, message: "Authorization header not found"} $(function() { var params = { // Request parameters 'username': '', 'password': '' }; $.ajax({ url: "https://services.widia.com/authentication/login?" + $.param(params), beforeSend: function(xhrObj){ // Request headers xhrObj.setRequestHeader("Content-Type","text/xml"); xhrObj.setRequestHeader("Ocp-Apim-Subscription-Key","XXXXXXXXXXXXXXXXXXXXXXXXX"); }, type: "POST", // Request body data: "", }) .done(function(data) { alert("success"); }) .fail(function() { alert("error"); }); });
    Posted by Hidden Tue, 05 Nov 2019 16:51:46 GMT


You're not signed in. Please sign-in to report an issue or post a comment.