Authentication methods changed

[realcoloride]

Hello,

For the second time, it seems like characterai has switched to a new way of authentication.

[realcoloride]

From my search, it seems like atleast for google accounts, there is an id tokenand key associated with a token from the new endpoint of dj-rest-auth/google_idp/.

This produces a session token.

This is the endpoint in question.

For easier development purposes, I might have to switch to using the session token only and rework the README.md.

I will keep you updated.

[realcoloride]

Hello again,

Changing to char_token seems to be a viable solution. I will push a fix along with the readme.md tutorial soon.

[realcoloride]

I added a warning message if the token is not as the same size of char_tokens (40).

[realcoloride]

I've updated the code for mobile token gathering.

[realcoloride]

Relevant commits:
7cb8e59 and 46db79e.

Experimental version 1.2.5 was pushed, please let me know how it goes for you all.

[Asphyxiav2]

No id token

[realcoloride]

Hello, please read the entire issue. Id tokens and access tokens have been replaced with session tokens. See README.md.

[azureknight63]

Thanks for the update. Your changes seem to be effective. For the readme update, it seems that the access token is now under Local Storage > char_token.value as you described. The ID token is under Local Storage > uuid.

It also looks like char_token has a 1-month TTL property. It's hard to suggest a feature if character.ai is going to change authentication methods this frequently, but if it stabilizes then I would recommend including utility for updating the char_token.

Cheers.

[realcoloride]

I seem to have also detected that the newer chat interface uses a websocket whilst the old interface uses good old requests.
Might be interesting to open an issue related to it.