Parse-server: How do I set the login expiration time?

Created on 14 Jun 2017  ·  4Comments  ·  Source: parse-community/parse-server

How do I set the login expiration time?

stale

Most helpful comment

This is controlled with the config property sessionLength if mounting parse as express middleware, or with the environment variable PARSE_SERVER_SESSION_LENGTH

All 4 comments

Once a user logs in, a Session object is created - containing a "createdAt" and "expiresAt" parameter. The expiration time defaults to 1 year from creation and I'm not sure if you can change that somewhere.

What you could try:

  • Fetching the Session object and overwriting the "expiresAt" time
  • Creating a Cron job that would delete old Sessions every day

Can I change the default expiration time?
我是否可以变更默认过期时间?


     公司网址:http://www.mengsens.com/


                  广东梦森信息科技有限公司 -              廖晓清
         公司地址:广州市海珠区新港西路135号中山大学国家大学科技园B座1308室

     手机号码:139 2609 5308
     QQ号码 :187 2117 737
     主营业务:快递鸽 - 快递物流综合解决方案



 祝:生活愉快!一切顺利!

------------------ Original ------------------
From: "Martin Herman"notifications@github.com;
Date: Wed, Jun 21, 2017 05:43 PM
To: "parse-community/parse-server"parse-server@noreply.github.com;
Cc: "lxq20081128"lxq@mengsens.com; "Author"author@noreply.github.com;
Subject: Re: [parse-community/parse-server] How do I set the login expirationtime? (#3930)

Once a user logs in, a Session object is created - containing a "createdAt" and "expiresAt" parameter. The expiration time defaults to 1 year from creation and I'm not sure if you can change that somewhere.

What you could try:

Fetching the Session object and overwriting the "expiresAt" time

Creating a Cron job that would delete old Sessions every day


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This is controlled with the config property sessionLength if mounting parse as express middleware, or with the environment variable PARSE_SERVER_SESSION_LENGTH

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings