Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
2020-10-1109:11 PM
SoapEwsRestProvider user group access issue
Hi everyone, I was trying to extract alarms for different EBO user groups using SoapEwsRestProvider. In EBO, We have an admin user and several users under different groups, each with access to certain directories/paths.
I was testing if each user can only retrieve the alarms in their specified groups, and noticed that with every /GetToken request we created under different user credentials, the tokens returned were different but /GetAlarmEvents requests always return the same alarm events. I.e. After starting the REST endpoint, get token with user1 (User Group 1) credentials, /GetAlarmEvents request returns the alarms for User Group 1. Send /GetToken request again with user2 (User Group 2) credentials, send /GetAlarmEvents request with the updated token but the return alarms are still for User Group 1. It seems that the rest provider is stuck with the first logged in user's permission path, whether it be the admin's or the users with specific permission paths.
Does anyone know if there's any way to ensure consistent user group management in the rest provider? My SmartConnector service version is 2.4.23. Thank you!
Link copied. Please paste this link to share this article on your social media post.
2020-10-1407:15 AM
Hi @Anonymous user,
I suspect you may have found a defect in the way we cache for the REST Provider when it comes to dealing with alarms.
The REST Gateway, in it's attempt to not burden the underlying EBO server with too many requests, caches alarms in a central cache, and as additional requests come in, pulls from the cache and only polls EBO when required.
There is no 'user separation' in this cache, so everything is returned as you are seeing.
I will add this as a bug, and see about addressing it in an upcoming release.
Please feel free to email be at jeff.bowman@se.com if you would like to discuss this further.