I had a similar problem - see here: https://github.com/lyft/confidant/issues/262#event-3032884983 On

Thanks! I'd love to hear about that. In the meantime, I did find this gist: https://gist.github.

Yeah, I agree. The CLI currently can only add blind credentials, but I've been meaning to add

On 08.09.17 20:50, Ryan Lane wrote: Hey Ryan, > We've actually been looking at this at Lyft

We've recently released 1.10.0, which includes updates the the python requirements to patch for

Hi! I'm hoping this is the appropriate place for this post. Based on the information posted here

That's great Russ! I'm going to open an issue in github about being able to use key ARNs in

Thanks a lot for the detailed answer Ryan, In most cases, removing a service access from an IAM role

Interesting options. Thanks for all of the info. I'll need to digest that a bit. On Wed, Aug 31,

OK - great, I'll look for that info on the client. Thanks! On Tuesday, August 30, 2016 at 2:24:42

In chrome this manifests as a "ERR_CONNECTION_CLOSED" error. Normally I'd activate

Great. Let me know if you run into any issues. Happy to help! On Fri, Jun 24, 2016 at 11:06 AM, <

While preparing for the 1.1 stable release Lyft found a KMS authentication vulnerability in the

Through internal review and testing Lyft discovered a security vulnerability in version 1.0 (current

Hey Justin, Just to follow up on this, Andy Brody added SAML support to the v1.1 branch of Confidant.

For anyone that was having a similar problem, I chatted with Geo and we enabled the debug logs, which