Write up or otherwise document personal experience with developing/integrating MyUSA

[esgoodman]

It doesn't have to be well-written, but some notes on your experience with MyUSA will help me ask better questions of developers and integrator PMs. You can put notes in comments here, send them to Liz in email or Slack.

attn: @adelevie and @yozlet

[esgoodman]

Will help resolve #640.

[jackiekazil]

👍 .... @ultrasaurus, @mbland, @seanherron, @phirefly --- let us know if you have stuff to add to this!

[mbland]

18F/blog-drafts#177 has a bunch of my experience. Let me know if there's other aspects in particular you'd like me to address that aren't covered in that pending blog post.

[esgoodman]

@mbland I'm specifically interested in any unexpected hurdles, hard-to-answer questions, or support concerns you had during the process. The blog post emphasizes the upsides — thank you! 😊 — but here I'm trying to figure out where we need to improve.

[mbland]

There weren't any, really. Once I figured out the OAuth2 handshake, which isn't just a MyUSA thing, it was all a breeze from there. I just plugged the right URLs into the google_auth_proxy, and accessed the right API to get the email address, and boom! myusa_auth_proxy. The developer documentation was especially handy.

My only recommendation might be adding section to said dev docs about how to set up google_auth_proxy to use it. ;-) (Actually, watch out for the rename, per bitly/oauth2_proxy#85).

Aside from that: #634 and #573 (aka #650) are the only issues I personally encountered so far.