How to persist URL hash fragments across a login redirect

I just spent four hours figuring out the ins and outs of URL hash fragments. On my team we use AngularJS to build some pretty cool single page applications. In a couple of our single page apps we use Angular routes to load various views. By default Angular uses the URL hash fragment to maintain client-side page state while still allowing the user to use the browser's forward and back buttons.