Not able to use the OTCSTICKET inside our server WIN2012R2 getting the error Authentication required but we are able to get in our local and postman.
Local Machine has WIN10EnterpriseOS
we are using windows service It's not a web application
Are you talking about Content Server(Livelink) or OTDS(Tomcat) they are different?OTCS has a windows service that starts and stops the service but Livelink/Content Server which accepts OTCSTicket cannot run without a webserver.OTDSTicket provided by TomCat is also a web application server it also has a windows service if installed there. If you are unsure and are not an administrator two screencaps your livelink runs IWA then create another application like above and put "anonymous" for that
Or are you saying there is an application that someone has developed that runs under windows services then also the above-ground rules matter if they are asking OTCSTicket it better be to an anonymously authenticated Livelink.
If you use IIS as the web server and enabled IWA for the CS CGI URL and do not want to disable it, see also other discussion about it.
open text server is working fine and the api is working is fine as expected from POstman tool and when tried from the code (VB dot net) its throwing the error our application is windows service
POstman tool is advanced if you get on a box with that VB Net application user's credentials it will without you knowing it supplies the header, it goes as NTLM authentication or IWA authentication. What @Ferdinand Prantl says in the other discussion is what you want, REST of OT will never work against a server (Livelink Application) when IWA is present.
OK so if you are that VB.NET programmer who wrote the piece try to run POSTman not as that user but in the POSTMan box put the VB.net service users credentials into the userid, password screens most likely if your livelink is IWA you will get authentication required.
To avoid all of this all you have to do is Right-Click the IIS web server and create a new application called it perhaps OTCSANON and point it to the cgi of livelink. Then make its authentication scheme anonymous, then run your rest. It clearly is a carryover from IIS when a server is created manually MS puts IWA by default, however, if your livelink application was created by the OT installer they would create it anonymous scheme. Anonymous does not mean anything terrible it just means people other than who are known to the DC (Domain Controller) can hit it...
#AOTD2D
If your service runs under LocalSystem or NetworkService and not under a domain user that can authenticate to the IIS, you face the same problem as discussed in the other thread.