-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not dumping users with guest role #108
Comments
Hey @jagarop, I'm trying to reproduce this, as my test workspace is on free account, I'm not able to invite guests, but I have one workspace where I have a guest account. What I've done so far - I exported a workspace where I'm a "guest", and users.json indeed does not contain some of the users, which are present in the channel conversations, and are resolved correctly by slack client. I'll see how this can be addressed. |
Hello @rusq, thanks for taking a look at this issue, really apreciate! If you need anything else from me that would help on this matter, please let me know. |
So I investigated quite a bit on this - the Slack Client calls a set of undocumented Slack edge APIs in order to retrieve the names of the users. I'm currently experimenting with this and made some progress, but it's far from completion. It is the same APIs that mentioned in #64. I'm parking it for now, as I think that implementing Mattermost export compatibility would take less time, and there's a high demand on that right now, as people are migrating from Slack to Mattermost (#107). I can only guess, that the reason that Slack does not return a complete set of users using the standard API and client token is that it does not expect someone to call standard Slack APIs under the guest account. |
Tested this with edge, the behaviour is the same - doesn't return all users, only those which guest has interacted with. Will need to check that kind of requests the browser sends, maybe it's possible to replicate. |
Describe the bug
Guest users information is not being dumped to users.json.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Populated guest users in users.json
Output
Not applicable
Desktop (please complete the following information):
Additional context
I tested this in a workspace that have about 400 normal users and 2000 guests. Got data for all normal users and no data from guests. It shows fine in browser/slack desktop client.
The text was updated successfully, but these errors were encountered: