• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

VK auth unexpected values in DB

Wink

Chevereto Member
▶🚶‍Reproduction steps
  1. Open phpMyAdmin
  2. SELECT * FROM `chv_logins` WHERE `login_type` = 'vk'
😢Unexpected result

`login_secret` have unexpected values
Are you sure what VK auth functions has no errors?

vkvk.png
 
The same applies to a login with Google.
A value is entered in the Facebook login.
But what it is all about I can not say, can only say that there have been no complaints so far that a login does not work.
Most likely, the login for some services will be compared directly so that there is no value in the database.

screenshot--2019.12.20-11-35-43.png
 
Hey @Wink

For Chevereto versions < 3.14, the login is made using $_SESSION and the cookies are used only as a token for setting the session variable. This means that the token array values don't matter, because these are required to re-connect to the social network. You can notice this when trying to login the same account from two different clients (browsers, computers, devices, etc) and you will see that only one session will be available at the same time, this is because each time you login doing social login it refresh everything, making old KEEP_LOGIN_SOCIAL cookie obsolete.

Starting from Chevereto 3.14 this system changes, and the actual tokens are now stored as these are used to skip the connection grant/access window and all the login is now cookie based, not PHP session. Besides from having more control and allow faster login, it allows to have multiple login sessions active and control login remotely as each login token exists as a row in the login table.

What I described above is already working in the demo, and the beta for this release should be available today.

Cheers.
 
Back
Top