Login callback failed after redirect for HashLocationStrategy

[lawchihon]

I'm submitting this issue for the package(s):

• [ ] jwt-verifier
• [X] okta-angular
• [ ] oidc-middleware
• [ ] okta-react
• [ ] okta-react-native
• [ ] okta-vue

I'm submitting a:

• [X] Bug report
• [ ] Feature request
• [ ] Other (Describe below)

Current behavior

Got an internal error for Unable to parse a token from the url

Expected behavior

Login without error

Minimal reproduction of the problem with instructions

1. Added useHash: true as options for RouterModule.forRoot
2. Adde logic to redirect implicit/callback to #/implicit/callback when page load
3. Call oktaAuth.loginRedirect

Extra information about the use case/user story you are trying to implement

Since the current Login redirect URIs cannot contain #, Im trying to redirect it back with # on customer side

Environment

• Package Version: 2.0.0
• Browser: Chrome
• OS: Mac
• Node version (node -v): v12.13.1
• Other:

[swiftone]

@lawchihon - Thanks for the report (and PR). We are thinking over how to handle this in all of our front end SDKs, not just angular, since anyone that returns to / after authentication will have issues - all hash-based routes will be on /, so we have to have a consistent way to know whether to look for tokens or not (and similarly, SOME / routes will require authentication)

Internal ref: OKTA-287878