Closed rmtobin closed 5 years ago
keithpitt
commented
6 years ago @rmtobin 👋 we hear you! I've been deep in re-engineering our SSO backend for the last few weeks to support this exact use case. We'll be shipping a private beta in a few weeks that should address the majority of issues with our current implementation! 🔜
keith
commented
5 years ago We'd like some solution to this too. Specifically user API keys that we use to trigger all of our builds. Right now we use a specific user's key but it really shouldn't be tied to a user. Whether or not we had a bot account or just a pipeline / org wide key wouldn't matter but either would work!
keithpitt
commented
5 years ago This is a thing now!
You can control on a per-user basis if SSO is required. So in the case of bot users, you can just mark them as "SSO optional" and use regular username/password for login.
Additionally, if you email support we can give you a 1 user discount for robot users.
I hope this helps! :rocket:
We set up a bot user in Buildkite for things like scheduled builds and non-user-specific API keys, however since we use Google SSO, we had to make a Google account for this bot user.
It'd be nice if we could create users directly in Buildkite without needing to set up a Google account.