I am working on a lyrics application that is made up of 3 separate applications. These are:
- Elm single page application
- .NET Core API
IdentityServer 4 is used to handle authorization and authentication requirements. For example, when my application is “complete”, users will be able to sign up and have the ability to submit new artists and lyrics.
The IdentityServer 4 team have created this frontend library called oidc-client-js that is supposed to help with the complexities of token management in the frontend.
I suspect such a thing does not exist for Elm. What are my options for getting my Elm SPA behaving and working with IdentityServer4?
The flow is that when a user clicks the login button, they get redirected to the IdentityServer4 login page, which in effect is a separate website/application. Once the user logs in, he/she will be redirected back to the Elm SPA and that’s where oidc-client-js usually kicks in to do whatever it has to do, and I suspect my Elm code has to do things too because I need to pass the
token with each API request after that.