# Consuming a REST service with Windows Integrated Auth (NTLM) from Integration Server 10.3 on Linux **URL:** \ **Category:** Forum\ **Tags:** NTLM, linux\ **Created:** [September 21, 2020, 5:40pm UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938 "2020-09-21T17:40:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Feng\_Sian5](https://avatars.discourse-cdn.com/v4/letter/f/b19c9b/32.png) [@Feng\_Sian5](https://techcommunity.softwareag.com/u/Feng_Sian5)\ **Post date:** [September 21, 2020, 5:40pm UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/1 "2020-09-21T17:40:24Z")
Hi Folks, I’m looking for how to consume a REST service that employs Windows Integrated Authentication, from an Integration Server 10.3 hosted in a Linux box. From the ‘10.3 IS Administrators Guide’, page 1170, says _“[…] When acting as a client, Integration Server responds to an NTLM challenge from a web server with the appropriate authentication credentials, whether **Integration Server** runs on Windows, **UNIX** , or another supported platform.”_ Having this said, has anyone got success in consuming a REST service that requires NTLM auth, **from an IS** [10.3] **running on a Linux box**? Additional info: - during the attempts, we’ve switched the authentication method to use `Basic Auth` and the IS consumes the service (through the `pub.client:http` service) swiftly. Therefore, the issue is indeed the authentication; - switching the auth method back to “Windows Integrated Authentication” it refuses to work, throwing error (the error message is not the original one, it is ‘wrapped’, saying that “non-trusted login is not accepted”); - and one of the tests involved setting the pub.client:http’s input as below, and it didn’t work out. ```auto auth/type = "NTLM" auth/user = "\" ``` So… any thoughts? ---
**Author:** ![Jaideep](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/jaideep/32/15623_2.png) [@Jaideep](https://techcommunity.softwareag.com/u/Jaideep)\ **Post date:** [February 16, 2021, 6:25am UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/2 "2021-02-16T06:25:56Z")
Hi Feng Sian, What is the IS Core fix level? Can you try using DOMAIN/user or user@DOMAIN format while sending the request via pub.client:http? ---
**Author:** ![Jaideep](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/jaideep/32/15623_2.png) [@Jaideep](https://techcommunity.softwareag.com/u/Jaideep)\ **Post date:** [February 16, 2021, 6:28am UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/4 "2021-02-16T06:28:51Z")
The " Name Variations" format supported can be found at [The NTLM Authentication Protocol and Security Support Provider (sourceforge.net)](http://davenport.sourceforge.net/ntlm.html) ---
**Author:** ![Feng\_Sian5](https://avatars.discourse-cdn.com/v4/letter/f/b19c9b/32.png) [@Feng\_Sian5](https://techcommunity.softwareag.com/u/Feng_Sian5)\ **Post date:** [March 4, 2021, 5:56pm UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/5 "2021-03-04T17:56:04Z")
Sorry for the late response. It is on IS\_10.3\_Core\_Fix8. I’ve tried both formats (`DOMAIN/user` and `user@DOMAIN`) but none worked… ---
**Author:** ![reamon](https://avatars.discourse-cdn.com/v4/letter/r/b77776/32.png) [@reamon](https://techcommunity.softwareag.com/u/reamon)\ **Post date:** [March 4, 2021, 8:15pm UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/6 "2021-03-04T20:15:49Z")
> [@Feng\_Sian5](#): > > I’ve tried both formats ( `DOMAIN/user` and `user@DOMAIN` ) but none worked I assume you tried domain\user (backslash, not slash). > [@Feng\_Sian5](#): > > the error message is not the original one, it is ‘wrapped’, saying that “non-trusted login is not accepted”); Do you have access to the original message? I’ve had to learn over the years (repeatedly 🙂 ) to trust the error message. It often indicates exactly what the issue but we often misinterpret. Perhaps the original message will trigger an idea from someone. The BIS reference for pub.client:http has this description: > When using NTLM, Integration Server supports authentication for both HTTP and > HTTPS. Web server providing NTLM authentication must be configured to return the > response header WWW-Authenticate: NTLM and optionally the header WWW-Authenticate: > Negotiate. If the NTLM server returns only WWW-Authenticate: Negotiate header, then > authentication cannot proceed. ---
**Author:** ![Jaideep](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/jaideep/32/15623_2.png) [@Jaideep](https://techcommunity.softwareag.com/u/Jaideep)\ **Post date:** [March 5, 2021, 4:54am UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/7 "2021-03-05T04:54:31Z")
Hi @Feng_Sian5 , I would suggest to try again with latest IS 10.3 Core fix (IS\_10.3\_Core\_Fix14) and with format I mentioned earlier. ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [June 3, 2021, 4:54am UTC](https://techcommunity.softwareag.com/t/consuming-a-rest-service-with-windows-integrated-auth-ntlm-from-integration-server-10-3-on-linux/233938/8 "2021-06-03T04:54:53Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.