Smart Connector 2.5.4 - Get Root - EBO 2022

[esari]

Hello

We have updated Smart Connector to version 2.5.4. Now we have issue with Get root command. Normally customers or third party company don't have permission to root object of ES, but they have access right for sub folder.

Get root will response

{

  "Message": "Container Id not found"

}

If third party company cannot get root folder then they cannot use Get containers children from root, because they dont know what is the correct root id.

This have been working in 2.4.X version.

--

Esa

[ardak]

Hmm, very weird, there have been no changes to the Root handling.

Could you turn on EWS Consume logging(debug level) and try to capture the log output when this happens?

Thanks!

Armend

[ardak]

I haven't been able to reproduce this,

Did you also upgrade to EBO 4.0/2022?

Do all users exhibit the same behaviour?

BR

Armend

[esari]

Hello

Yes, Issue is related to EBO 2022. I tested with EBO 3.2 and it worked correcly. So no issue with Smart Connector 2.5.4 with EBO 3.2. Issue seem to be with EBO 2022. 

--

Esa

[ardak]

The issue seems to be related to semantic in EBO 4.0.1

EBO seems to try to access the root node of the system if "Enable semantic" is enabled in the EWS Server Configuration. If applicable in your use case, a workaround is to disable semantic in EWS.

An investigation is ongoing, more to come soon.

BR

Armend

[ardak · Accepted solution]

In EBO 4.0.1, if semantic is enabled and the user doesn't have access to the root of the server, EWS will return an error. This will be fixed in EBO 4.0.2.

A possible workaround is to turn off semantic in EWS Server Configuration if you do not need it.

BR

Armend