aurelia-auth | : key : Authentication plugin for aurelia | Authentication library

I just ran into the same issue, and the solution is described here: https://github.com/FezVrasta/popper.js/issues/287

My main.ts now looks like something like the following:

Here are a few things you can try:

• Chain the promises (make sure the navigation is done before you tell aurelia to switch the root)

token (or the object containing it) is expected to be the value of prop 'access_token' in the response by default in aurelia-auth

so you need to change the structure of your api response to

So after spending more time on this I was able to track the issue down and find a solution.

The solution was to change the aurelia-authentication authConfig postLogoutRedirectUri value to just the root page (http://localhost:8080). Additionally, I needed to define that URI under the PostLogoutRedirectUris within my IdentityServer4 Client definition.

logoutResponse was then coming through correctly with a property named state property that holds the correct value and permits the redirect successfully.

For Webpack:

In the webpack.config.js, there is a ModulesDependenciesPlugin entry within the plugins property. Add aurelia-auth in there, e.g.:

I was heading down the wrong path, you use the configuration object off aurelia-api to get an endpoint you can then call:

If you're using pushState you should add in head tag a base tag in your index.html or starting document. See it here for more configuration. It would look something like this

I needed to specify a callback route when initializing the Auth0Lock

I haven't used the aurelia-authentication plugin, but I can help with a basic technique you can use that makes this very easy. In your main.js file, set the root of your app to a "login" component. Within the login component, when the user has successfully authenticated, set the root of your app to a "shell" component (or any component you choose) that has a router view and configure the router in its view-model. Once this happens, the router will take the user to the proper component based on the url. If the user logs out, just set the app root back to the "login" component.

Here's some cursory code to attempt to convey the idea. I assume you're using the SpoonX plugin, but that's not really necessary. Just as long as you reset the root of your app when the user authenticates, it will work.

In main.js