Open danyoung opened 5 years ago
GitHub Oauth is indeed what we need. No special preferences for configuration, though it would be nice if we didn’t have to continually pass it to the CLI during updates.
How about a plain old LDAP authentication? I think that will have huge applicability in the Enterprise? OAuth is fine, but unfortunately in most places, it is not nearly as ubiquitous and reliable as LDAP.
@danyoung definitely Github auth. For us we have all our developers, PM's and DM's using Github, so makes perfect sense for us to use Github as our central authentication system for developer related systems.
Thanks again for looking into this
Thanks for the input folks. We have created a new Slack workspace to provide users with a place to ask questions, get support and discuss feature ideas: https://join.slack.com/t/concourse-up/shared_invite/enQtNDI1OTAwODczNDk0LTRkYTk0ZTg4NTliMDkzNWI3NjUwNzU3ZGE1YmQ1ZmQyMjlhMjVjNjI4ODUxMzM5OWJiNjRjYjZkMmI5M2RmNDQ
For those looking for GitHub oAuth support, this is now in the latest releases. Please check https://github.com/EngineerBetter/concourse-up/releases
The Concourse-Up team are considering ways of addressing the change to how Concourse 4.0 handles authentication providers. We are aware that these changes will have left users without a way to support their previous auth configuration.
To help us make decisions, please comment on this issue to let us know which authentication methods you need to support and any preferences you have for doing this via the Concourse-Up tool. We suspect that Github.com oAuth is going to be a popular method, but we'd like to confirm this.
Many thanks!
Dan