oauth.js | Javascript library used to easily request secured OAuth | OAuth library

You're using an absolute path

Solved by restarting from the new Svelte v3.0.0 template, upgrading other npm dependencies, adding @rollup/plugin/json and setting resolve.preferBuiltins to false.

rollup.config.js

At your script, the redirect URI is created like redirect_uri=http://localhost:8000/. In this case, the registered "Authorized redirect URIs" is different from it. By this, such error occurs. So in this case, please modify http://localhost:8000 to http://localhost:8000/ at "Authorized redirect URIs" as follows and test it again.

• And, in this case, it seems that even when http://localhost:8000 and http://127.0.0.1:8000 of "Authorized JavaScript origins" are removed, the authorization works.

You need to add the authenticate middleware in the callback route as well. You can check out the docs here:

You have been given absolutely woeful instructions.

I registered an account with your OAuth provider and as you say, there were no instructions provided on what URL to use but with a little trial and error, I found you need to provide the app_id query string parameter. For example

getVirtualServerName() was added in Servlet 3.1, but you included servlet-api-2.5.jar is your application.

Options:

• Change your dependencies to include servlet-api-3.1.jar (or later)

• Remove the servlet-api-2.5.jar dependency, since the correct version is included in the Embedded Tomcat file (tomcat-embed-core-9.0.33.jar).

Actually, you should never ship servlet-api.jar with your application, since it will be provided by the Servlet Container. Seems you're missing provided in your dependency tag for the servlet-api file.

This was caused by Blizzard issuing their tokens from their well-known endpoints but setting the iss field to oauth.battle.net which caused Cognito (or any other token validation) to fail hence the error message

Bad+id_token+issuer+oauth.battle.net

I brought this up to their API team in Discord and they are releasing a fix on November 25th according to an email send to developers.

Dear community developer,

Earlier this year, we introduced a new OAuth discovery endpoint which implements the OpenID Connect discovery specification. We would like to deploy a change to the issuer field iss of the id_token during the OpenID authorization flow from oauth.battle.net to the issuer that is returned by the well-known configuration endpoint JSON response. This would be a potential breaking change to some of the OAuth OIDC clients but it conforms to the OpenID connect specification: https://openid.net/specs/openid-connect-core-1_0.html#IssuerIdentifier

Your OAuth client application was identified as one that could be affected by this change.

We are planning to release this change on November 25, 2019.

Here are the steps that you can take to ensure your OpenID Connect client will continue working after the change:

Navigate to one of the well-known configuration endpoints below which corresponds to the region where your client application operates and check the "issuer" field.

If the issuer field matches the configured issuer for your OAuth OIDC client then your client is compatible and you are already compliant and do not need to make any changes.

If the issuer field from the well-known configuration endpoint is different than the issuer set in your client configuration, please change the issuer to match the well-known configuration endpoint.

If your client supports the OpenID discovery endpoint standard, you can configure it to read all necessary settings from the well-known configuration endpoint. Your OAuth client should self-configure.

As mentioned in the documentation, this library does not include any of the CSS for Font Awesome and expects you to add it to the project yourself.

If you prefer a CDN, you can add it from here

Updated Sandbox (Note the external resources has a font-awesome CSS file)

You can add it to index.html with:

You cannot use Twilio library inside Angular project.

This is caused by dependencies importing node modules that are not available in the browser. Add to your package.json the modules that give errors: