(TXT) / (IMG) - Add visual results and more info.

Author: davidjguru

_posts/2022-03-30-drupal-tips-changing-session-lifetime-for-users.md

@@ -2,7 +2,7 @@
 layout: post
 title: 'Drupal Tips: Changing session lifetime for users'
 permalink: /blog/drupal-tips-changing-session-lifetime-for-users
-published: false
+published: true
 date: 2022-03-30
 author: davidjguru
 categories: [Drupal Tips]
@@ -104,7 +104,7 @@ This value is for the browser: This is the absolute maximum time till which a br
 | :-------------------------------------------------------------------------------------------------------------------:        |
 |              *Cookie values for creation and expiration dates*                                           |
 
-By default is set with 2,000,000 seconds, equals to almost 24 days. See the previous caption with creation and expiration date, so for a cookie created on March 27th, we can see an expiration date of April 19th, which is just a 23-day life cycle, the marked 2,000,000 seconds.  
+By default is set with 2,000,000 seconds, equals to almost 24 days. See the previous caption with creation and expiration date, so for a cookie created on March 27th, we can see an expiration date of April 19th, which is just a 23-day life cycle, the marked 2,000,000 seconds. You can think about change this data in service.yml files, but It's true that these kind of files is out of control for Git so your changes will not be shared with your team, and it won't be recreated in common environments (stage, preprod, prod, live, etc). You'll need a more "structural" and persistent solution, so we will need to create a new custom module in next steps.   
 
 ## Addressing session cookie management in Drupal
 
@@ -160,10 +160,7 @@ public function alter(ContainerBuilder $container) {
   }
 ```
 
- 
-
-A new custom Drupal module has been implemented for alter the session data: st_session_manager, available in branch 
-
+ Here you can see and download [the custom module implemented as example and uploaded to my Gitlab repository](https://gitlab.com/davidjguru/drupal-custom-modules-examples/-/tree/master/custom_session_manager). Check out the code and test the feature! (not for production - live environments, please).
 .
 
 So now: 
@@ -175,25 +172,43 @@ $options['cookie_lifetime'] = 0;
 $options['gc_maxlifetime'] = 3600; 
 ```
 
-## Useful Modules
+And just enabling this new custom module, you will have a key change here: now the max-age of the session cookie will be set for expiring by session, see:  
+
+| ![Max-Age for cookie set to Session]({{ site.baseurl }}/images/davidjguru_drupal_8_9_changing_session_lifetime_for_users_3.png) |
+| :-------------------------------------------------------------------------------------------------------------------:        |
+|              *Max-Age for cookie set to Session*                                           |
+
+Now when you close your browser, the session cookie will be deleted, the user logout will be executed and on the next URL load, the user session will still be closed.  
+
+
+
+## Session data & Garbage Collector & Cron
+
+You can load the session time with the values you want. But this only let available the session data for the Garbage Collector of Drupal/PHP. It means that from 1 hour the session can be opened until the Garbage Collector was executed. Who’s executing the Garbage Collector? essentially, the cron in system. The “Automated Cron” core module can be enabled and set to 1 hours. It means that really, the inactive sessions (more than 1 hour without activity) will be deleted every 1 hour now, just when cron runs and launches the Garbage Collector.  
+
+But perhaps, we need a little more "granularity." that is, to launch the cron only for these specific tasks, because launching it completely and for everything very frequently may not be the good idea we were thinking of. We need to be able to filter tasks associated with the cron in a more atomic way. For this we can rely on certain Drupal contributed modules that can provide us with functionality.  
+
 
-Session data & Garbage Collector & Cron
+### Useful Modules 
 
-The time for session was set to 1 hour.  But this only let available the session data for the Garbage Collector of Drupal/PHP. It means that from 1 hour the session can be opened until the Garbage Collector was executed. Who’s executing the Garbage Collector? esentially, the cron in system. 
+Useful Drupal contrib modules we can use for more control over the session timing, roles and garbage collector from cron executions:  
 
-The “Automated Cron” core module was enabled and set to 1 hours. It means that really, the inactive sessions (more than 1 hour without activity) will be deleted every 1 hour now, just when cron runs and launches the Garbage Collector. Useful Drupal contrib modules we can use for more control over the session timing and roles: 
+1. Session Limit: [drupal.org/session_limit](https://www.drupal.org/project/session_limit). You can limit the number of sessions available for a role / user in different environments.  
+   
+2. Automated Logout: [drupal.org/autologout](https://www.drupal.org/project/autologout). You can configure sessions settings values in order to force the logout in users.  
 
-1- Session Limit: https://www.drupal.org/project/session_limit 
+3. Ultimate Cron: [drupal.org/ultimate_cron](https://www.drupal.org/project/ultimate_cron). It Allows refinement in cron timing and execution's tasks.  
 
-Limit the number of sessions available for a role / user in different environments.
 
-2- Automated Logout: https://www.drupal.org/project/autologout 
+Futhermore, we can create some specific cron-tab tasks on the server by prompt, if we need more control over the session data. Cron is a time-based job scheduling daemon in Linux Operating Systems. You can learn more about how to configure tasks in background using cron here:  
 
-Set values in order to force the logout in users. 
+* [How to setup cron jobs in Ubuntu](https://www.geeksforgeeks.org/how-to-setup-cron-jobs-in-ubuntu/)  
+* [How To Use Cron to Automate Tasks on Ubuntu](https://www.digitalocean.com/community/tutorials/how-to-use-cron-to-automate-tasks-ubuntu-1804)  
+* [How to Automate Regular Tasks with Cron on Ubuntu](https://serverspace.io/support/help/automate-tasks-with-cron-ubuntu-20-04/)  
 
-3- Ultimate Cron: https://www.drupal.org/project/ultimate_cron 
+## :wq!
 
-Allows refinement in cron timing and tasks. 
+### Recommended song: I Feel So Good - Joanna Connor
 
 
-Futhermore, we can create some specific cron-tab tasks on the server by prompt, if we need more control over the session data.
+{% include youtubePlayer.html id=page.youtubeId %}