25 May 2017

Launched: Single sign-on

Spend some time at a software shop, and you’ll inevitably collect a pile of accounts for services, internal and external. Since you value security, each of your passwords are long and unique and safeguarded in a password manager. You imagine a world where you don’t need to manage passwords for each and every service you use.

That’s why we are excited to announce support for single sign-on via the industry-standard Security Assertion Markup Language 2.0 (SAML 2.0). Knowing that SAML integrations can be cumbersome and complicated, we refined the administrator experience to be simple and clear. We built a test-drive mode so administrators can verify their SAML configuration end-to-end before enabling single sign-on in LaunchDarkly for the entire team.

Our single sign-on implementation is accompanied by a couple other benefits. With LaunchDarkly’s just-in-time user provisioning, administrators can onboard new employees from their identity provider without having to also create accounts for them in LaunchDarkly. Simply grant the new employee access to LaunchDarkly via your identity provider. Then LaunchDarkly will automatically create a new account when the member visits LaunchDarkly for the first time. Additionally, any changes to the member’s profile or assigned roles will be propagated from your identity provider as soon as the member signs into LaunchDarkly.

We currently support Okta and OneLogin, with support for additional identity providers on the way.

Single sign-on is available to customers on our enterprise plans. If you’re interested in learning more about our enterprise plans, contact sales@launchdarkly.com.

Behind the curtain

Alexis and I collaborated on the single sign-on feature. The very first step we took was creating a feature flag for SSO in LaunchDarkly. With our feature flag seatbelt on, we didn’t need to maintain a long-running branch for the feature, which meant we thankfully didn’t have to suffer from massive merge conflicts. Every optional change that could be hidden behind that feature flag could be released incrementally and without extensive manual QA review.

When we demonstrated the feature in progress to a customer, we didn’t need to use a staging system; we could demo on production because the feature was hidden behind a feature flag. When we were ready for the feature to be beta-tested, it was very easy to enable it for one customer and then another. The SSO feature flag remains today, and now our sales team uses the flag to enable the feature for their customers.

19 Jan 2017

My first week is in the books

Like coming home

At the end of my first week with LaunchDarkly, not one but two teammates separately remarked that it felt like I had been with LaunchDarkly for a year now. In a way, that was true since I had been a customer and internal champion for at least that long. But I had only just arrived last Monday to find a shiny new laptop and desk with my very own LaunchDarkly t-shirt. On the previous Friday, I received notes from Edith and John about how excited they were for me to start. I had never felt so welcomed on my first day at a new job as I did here!

The team is still small enough that I met the entire company in a couple minutes and felt like I clicked with everyone instantly. I can tell everyone is seasoned and fully engaged in the company, wearing at least two hats at all times — yet we also find plenty of occasions to laugh. I know I’ll need to step up my comedy game to keep pace. Like a family, we have lunch together every day and share what’s going on in our lives, but unlike a family, there’s no drama and dysfunction.

Our space at Heavybit is great — lots of natural light, a cozy feel on even a cool winter morning, and plenty of warm woodwork. The quirky yet stylish decor makes me feel at home, even though I come here to work. I also love that there’s a communal feel to the space, a community among startups.

ABC: Always Be Coding

My first week included a tremendous amount of pairing to get my development environment up and running, but by the end of the week, I also managed to fix a few bugs, review some code, and deploy to production. They even let me get my feet wet with a few support tickets! I love how fiercely agile the team and all our processes are. We’re using new tools and services I’ve never even heard of before. If it might possibly help us, we try it. I’m looking forward to shipping new features in LaunchDarkly and exploring how these third-party services can help us move even faster.

Right time, right place

I joined LaunchDarkly as employee #12, the fourth new hire in about a month. For me it’s an exciting time to be here, having an opportunity to help shape our values and culture and witness the realization of our future home. This rocket ship is about to lift off, and I’m psyched to be aboard for the ride.