William Richardson

Glad it helped @LucasCioffi . @julienma , If you get a chance to try out my fork, let us know if it helps or breaks. I think it covers all...

Hey @manuraj17, Based on the "code_already_used" error, it looks like omniauth (or something) is requesting the token a second time. Is this happening only with the ginjo fork or also...

@manuraj17 no worries, glad you got it working! Let me know if see the issue happen again.

Hi all, @SirRawlins, My fork (ginjo) attempted to address all of the current scoping and data-retrieval issues at the time I created it. Unfortunately, I haven't brought it up to...

Sorry, my bad! I renamed my ```auth-hash-fixes``` branch to ```features-and-fixes```, since the work I've done has expanded beyond the auth-hash object. If you delete & reload (re-bundle) my ```/ginjo/omniauth-slack``` fork...

@JustLey, If I understand correctly - which I may not :smile: - it sounds like you are using different omniauth provider 'aliases' (same Slack, but different omniauth provider lable with...

I'm still trying to make sense of Slack's different api-flows myself. Even though they have lots of good documentation on each type, I still can't visualize the full difference. It...

Hi @samst-test , no problem. I'll look into my code and see what I can find. I've been focusing on some other stuff the last few months, but I've been...

Hey @samst-test - Unfortunately, I'm not familiar with Devise, as I use my own authentication management library based on Warden and Omniauth. But here's what I'm doing to handle the...

Following up with my initial post, I'm expanding the focus of my initial concern to include more of the raw oauth2 response information returned from Slack. Currently omniauth-slack populates the...