Closed atymic closed 9 months ago
I've PR'd a fixed provider to the socialite providers repo, which allows you to set both scopes, and gives you the ability to access the raw token response via socialite's accessTokenResponseBody
on the user object.
https://github.com/SocialiteProviders/Providers/pull/1136
I guess making it work as the above PR would be a breaking change, so open to something else
This might be best reported to https://github.com/SocialiteProviders/Providers
@crynobone this is actually an issue with this provider. I just copied the provider for that PR, but ideally we'd update this as it's the main provider.
@crynobone I believe this issue needs to be reopened as it concerns the official Slack Socialite provider. Furthermore, the socialiteproviders/slack package is flagged as deprecated and directs users to the official Slack Socialite provider for substitution.
@m1guelpf could you please un-archive the slack provider? I will update the docs https://packagist.org/packages/socialiteproviders/slack
@atymic done
@maartenpaauw docs are updated now and unarchived :)
Thanks @m1guelpf :)
Slack's API allows you to pass both
user_scopes
andscopes
in the same request. When receiving the access token body, it will have both tokens.Currently it's not possible to get both tokens, as if you set user scopes the bot scopes are null'd out.
I propose adding a new method,
withUserScopes
. When this is set alongsideasBotUser
, the both the access token for the user and the bot access token will be returned.If anyone else has a better suggestion let me know.
cc @ataldev