Skip to content
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

Customize slack/install page for Oauth #975

Closed
4 of 10 tasks
tdottin opened this issue Jun 28, 2021 · 2 comments
Closed
4 of 10 tasks

Customize slack/install page for Oauth #975

tdottin opened this issue Jun 28, 2021 · 2 comments
Labels
question M-T: User needs support to use the project

Comments

@tdottin
Copy link

tdottin commented Jun 28, 2021

Description

Describe your issue here.

What type of issue is this? (place an x in one of the [ ])

  • bug
  • enhancement (feature request)
  • question
  • documentation related
  • example code related
  • testing related
  • discussion

Requirements (place an x in each of the [ ])

  • I've read and understood the Contributing guidelines and have done my best effort to follow them.
  • I've read and agree to the Code of Conduct.
  • I've searched for any related issues and avoided creating a duplicate issue.

When implementing OAuth is there any way to customize the html for slack/install route auto generated by Bolt? As I understand it the "Add to Slack" button on this page needs to be used (#939) but we would like to include more information/custom branding for our customers. I considered embedding it into our existing web application via iframe, but this results in slack.com refused to connect error on click.

@gitwave gitwave bot added the untriaged label Jun 28, 2021
@misscoded misscoded added question M-T: User needs support to use the project and removed untriaged labels Jun 30, 2021
@misscoded
Copy link
Contributor

misscoded commented Jun 30, 2021

Hi @tdottin! Thanks for bringing this question to us -- it's resulted in a solid conversation amongst the maintainers about the best path forward for this issue, as it's certainly not the first time it's been raised and we completely agree that it should be supported.

We've opened a new issue (#977) that outlines a workaround that should work until a fix is introduced. Have a look and let us know if that suits your use case for the time being. When the associated PR is introduced, we also welcome you to participate in the review to ensure we're checking all the boxes!

And, of course, if you have any further questions, feel free to let us know! 🙂

@tdottin
Copy link
Author

tdottin commented Jun 30, 2021

Thanks @misscoded this makes sense and the workaround suits my use case. Will stay tuned on the new issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question M-T: User needs support to use the project
Projects
None yet
Development

No branches or pull requests

2 participants