Trouble connecting from the Unity API to an app server that uses Windows authentication in OnBase EP3

[Tim_Sanders]

We are starting to upgrade to EP3 from OB 18. We have a number of app server urls and one of them is set to use Windows authentication.
We haven't had trouble connecting via the Unity API to it in past versions of OnBase, but we are having trouble connecting to the Windows authentication configured app server url. Connections to the other urls are working using the same code. 

I have tried using both OnBaseAuthenticationProperties and DomainAuthenticationProperties to authenticate.
Both fail to authenticate.

Has anyone experienced this issue or know of a fix for it?

Thanks!

Here's an example of the error:

Exception: null

Exception in thread "main" Hyland.Unity.UnityAPIException: An error occurred within the Unity API

---------------------

Server Source: null

Server TargetSite: null

Server Exception: null ---> null

        at Hyland.Unity.Application.Execute(Application.java:933)

        at Hyland.Unity.Application.Execute(Application.java:904)

        at Hyland.Unity.Application.ExecuteWithValidation(Application.java:829)

        at Hyland.Unity.Application.Disconnect(Application.java:812)

        at edu.umich.med.doc.onbase.unity.connect.Connectable.forceDisconnect(Connectable.java:108)

        at edu.umich.med.doc.onbase.scripts.UnityQueryDocuments.main(UnityQueryDocuments.java:95)

Caused by: java.io.IOException: Unauthorized

        at Hyland.Services.OptimizedSoapServiceClient.executeVersion2(OptimizedSoapServiceClient.java:331)

        at Hyland.Services.OptimizedSoapServiceClient.Execute(OptimizedSoapServiceClient.java:114)

        at Hyland.Unity.Application.Execute(Application.java:928)

        ... 5 more

[Andy_Heller1]

Tim,

Did you ever get a solution to this?  We're seeing a similar issue on an upgrade to EP3

[Manohar_Nimmala]

We are getting similar issue. Is there a solution?

Hyland.Unity.UnityAPIException: An error occurred within the Unity API
---------------------
Server Source: null
Server TargetSite: null
Server Exception: null ---> null
at Hyland.Unity.DomainAuthenticationProperties.ConnectAndGetIntegrationApplicationOptions(DomainAuthenticationProperties.java:119)
at Hyland.Unity.Application.Connect(Application.java:666)
at com.kyfb.onbase.OBServiceSession.connectUnityApi(OBServiceSession.java:80)
at com.kyfb.onbase.OBServiceClient.storeDocument(OBServiceClient.java:189)
at com.kyfb.onbase.unity.test.OBUnityServiceClientTest.testStoreDocument(OBUnityServiceClientTest.java:313)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:542)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:770)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:464)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:210)
Caused by: java.lang.NullPointerException
at Hyland.Services.OptimizedSoapServiceClient.Execute(OptimizedSoapServiceClient.java:105)
at Hyland.Unity.AuthenticationProperties.executeConnectRequest(AuthenticationProperties.java:328)
at Hyland.Unity.DomainAuthenticationProperties.ConnectAndGetIntegrationApplicationOptions(DomainAuthenticationProperties.java:115)
... 30 more

[Cindy_Catalano]

We had an issue very similar to this when we upgraded from 18 to EP5. In order for our Hyland API apps to connect via windows auth, we had to make the following changes, and Hyland also recommened rebuilding the apps with the new EP5 API files:

 In the WEB.CONFIG file, set UseOSAuthentication to false and uncomment the AuthService node;

in IIS MANAGER, set Anonymous Authentication to enabled and Windows Authentication to enabled; at the AUTHSERVICE.ASMX LEVEL, set Windows Authentication to enabled.

Making the above adjustments allowed our Hyland API apps to connect using Windows Auth.

[Manohar_Nimmala]

Thank you for your response. We tried to change these settings as Cindy suggested. We couldn't find some options as you suggested. Here is the screen shot. We are trying to upgrade to EP3 and using 20.2.3 version.