# Changing signing algorithm doesn't work

**URL:** <https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908>\
**Category:** Get Help\
**Tags:** dashboard, algorithm\
**Created:** [June 5, 2017, 5:59pm UTC](https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908 "2017-06-05T17:59:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sharok89](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sharok89](https://community.auth0.com/u/sharok89)\
**Post date:** [June 5, 2017, 5:59pm UTC](https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908/1 "2017-06-05T17:59:32Z")

</div>

I have selected HS256 algorithm:

![alt text][1]

And, I saved changes:  
![alt text][2]

I got a new token, but when I read info [jwt.io](http://jwt.io) shows RS256:  
![alt text][3]

This is the code that I use for login:

```
this.auth0.client({
      realm: 'Username-Password-Authentication',
      responseType: 'token',
      username: credentials.username,
      password: credentials.password,
      scope: 'openid profile email'
    })

```

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [June 5, 2017, 8:12pm UTC](https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908/2 "2017-06-05T20:12:35Z")

</div>

As specified in the documentation the Auth0.js v8 `webAuth.client.login` method performs a resource owner password credentials (ROPC) grant using the `/oauth/token` endpoint.

> (…) database connections, using `/oauth/token`.

The documentation for [ROPC](https://auth0.com/docs/api-auth/tutorials/adoption/password) then indicates that `/oauth/token` endpoint is the equivalent endpoint to `/oauth/ro` when you are using the currently recommended OpenID Connect (OIDC) compliant endpoints.

If you look further at the [authentication response](https://auth0.com/docs/api-auth/tutorials/adoption/password#authentication-response) notes available in the documentation for the OIDC compliant response you’ll see the following:

> The **ID token will be forcibly signed using RS256** if requested by a [public client](https://auth0.com/docs/api-auth/client-types#public-clients).

In conclusion, what you’re observing is the expected behavior as I’m assuming you’re performing that call from what can be considered a public client.

---

<div class="post-metadata">

**Author:** ![sharok89](https://upload.wikimedia.org/wikipedia/commons/thumb/7/7c/User_font_awesome.svg/768px-User_font_awesome.svg.png) [@sharok89](https://community.auth0.com/u/sharok89)\
**Post date:** [June 6, 2017, 4:41pm UTC](https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908/3 "2017-06-06T16:41:45Z")

</div>

The Auth0 documenttion is most terrible documentation in my life. Thank you for the answer.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:54am UTC](https://community.auth0.com/t/changing-signing-algorithm-doesnt-work/6908/4 "2018-03-02T05:54:23Z")

</div>


