InfoGo sharing question
I have both security and sharing enabled on InfoGo SSRM.
Security is AuthNT and out organization's domain is identified in the Settings file. This works. InfoGo recognizes our domain accounts and identifies us by domain usernames when any of us go to the InfoGo app.
However, when we try to share reports, we get a list of 3 sample names and 1 sample group called "Presidents" to share with.
We're looking to share with users and groups in our org's domain. Where do the list of sharing users/groups come from? It doesn't seem to be picking up our domain active directory by default.
-
The sharing list is configured in the goCustomizations.goBookmarkSharingUserList definition sharedDataLayer shared element.
My guess is that you will need a Connection.LDAP in your _Settings.lgx and then use a Datalayer.LDAP to query the Users and Groups for Sharing.
https://devnet.logianalytics.com/hc/en-us/articles/4419715365015-Sharing-with-Groups-of-Users0 -
That answer helped advance me a little. Here is what I found so far...
You need to modify the goBookmarkSharingUserlist report that is part of the InfoGo application. Inside this report is a sharedDataLayer and Sharing List that the goHome report uses to pop up the list of users to share with.
So I need to figure out how to modify the sharedDataLayer to produce a result set of employees within our organization.
What's odd is when I change one of the sample data records to my Username, it no longer shows as an option to share with. However, if I give the record a fake non-existent Username, it shows it as an option to share with (even though no such user exists).
0 -
You cannot share with yourself. So if you are logged in with your username, your username is automatically filtered from the sharing list
0 -
Ahh, nice. Well in my mind that confirms to me that I entered a static row with correct data. The next test would be to re-enter my real Username as a static row and see if another employee in the organization sees me.
If that works, then the final step will be re-creating the dataset from an AD query as opposed to building it statically.
0
Please sign in to leave a comment.
Comments
4 comments