How to avoid re-logging in using securesocial on the play 2 platform?

I use "SecureSocial" for authentication in my project. I have a problem that was half responded to a stack overflow. Whenever I update my project (due to a file change, etc.), I have to re-register. The following are related questions:

On both issues, this behavior is blamed on the SampleUserService, which is based on memory. I can understand that. In my case, I implemented my own UserService, which saves user login data to the database (I know this because when updating the project I do not need to re-register and only need to log in). This is quite annoying and takes a lot of time to develop. To overcome this, someone answered the second question as follows:

"SecureSocial by default uses the default cache to store authenticators (which correspond to cookies for a registered user). The game’s default cache is EHCache and it is configured using ehcache.xml, which you can find in banks. The default configuration is strict in memory, which means that when you restart the application, it loses all values. Fortunately, it’s pretty easy to overwrite the EHCache configuration for writing to disk. "

Having said above, I have the following questions:

  • , EHCache , , , . , 500 000 ( ) 10 , . , 500 000 ? , , facebook linkedin ..,..., - ?

  • , , ( EHCache). . / ? , , . , , 500 000 ?

- , . , - .

+4

Source: https://habr.com/ru/post/1530124/


All Articles