How Lithium treats # in the SSO URL is a problem

Lithium is investigating this but say that a hashtag in a URL is interpreted as a fragment indentifier, and so it get redirected as follows:

For single sign on we have our login page here (developed with angular js) https://www.carfax.com/community/#/join . I put that link in the Lithium Admin panel under system > SSO. 

Lithium redirects as follows: 

https://www.carfax.com/community/?referer=http%3A%2F%2Fcommunity.carfax.com%2F#/login

What we need it to do is this: 

https://www.carfax.com/community/#/login?referer=http%3A%2F%2Fcommunity.carfax.com%2F

This is so we can implement the token so that when a non registered or non logged in user attempts to click on reply or like to a post, he/she is sent to the login page, and then taken back to where they were (say a forum post).