New Member
Brethren, is is possible to add a feature so that members can stay logged into their Gospel Library account for longer periods of time?
I understand the necessity of the auto-logout for the Member Directory and other tools with sensitive content. But I must say that logging in/out every 30 minutes while I'm trying to create a talk, having online discussions, etc. is very frustrating.
Is it possible to have an IDP setup where we have TWO IDs: one for sensitive content and one for non-sensitive content (like my scriptural notes - which I use ALL THE TIME)? BOTH would reset on login, but the more sensitive ID would expire in 30 minutes? The other would expire in a day or something like that (or 2 weeks like some websites).
This is possible to do, TECHNICALLY, and it's something that we really SHOULD do in order to decrease the frustration for members who use our MARVELOUS Gospel Library.
Using OAuth 2.0 / OpenID Connect
The IdP issues:
Access Token → expires in 30 minutes
Refresh Token → expires in 24 hours
When the user logs in again, you can configure the IdP to:
Invalidate all previous tokens
Issue new ones with fresh expiration times
Most IdPs (Okta, Auth0, Azure AD, Keycloak) support this pattern natively.
Using SAML 2.0
You can control AssertionLifetime (short-lived, e.g., 30 min)
The session cookie or IdP session index can persist for 24 hours
Logging in again invalidates both assertion and session
SAMPLE YAML
access_token:
expires_in: 1800 # 30 minutes
refresh_token:
expires_in: 86400 # 24 hours
on_login:
revoke_existing_tokens: true
This would be a HUGE blessing to members who use our Gospel Library to prepare talks, lessons, research the scriptures, add notes and links, etc. I can't possibly tell you how frustrating it is to write up a whole note in the Gospel Library and then when I go to SAVE my work, I'm told that I've been logged out. I've lost a LOT of inspired content as a result of this issue. I'd be SUPER grateful if you could implement a dual-authentication structure like the one defined above.
Robert Husted
rhusted@gmail.com
I understand the necessity of the auto-logout for the Member Directory and other tools with sensitive content. But I must say that logging in/out every 30 minutes while I'm trying to create a talk, having online discussions, etc. is very frustrating.
Is it possible to have an IDP setup where we have TWO IDs: one for sensitive content and one for non-sensitive content (like my scriptural notes - which I use ALL THE TIME)? BOTH would reset on login, but the more sensitive ID would expire in 30 minutes? The other would expire in a day or something like that (or 2 weeks like some websites).
This is possible to do, TECHNICALLY, and it's something that we really SHOULD do in order to decrease the frustration for members who use our MARVELOUS Gospel Library.
Using OAuth 2.0 / OpenID Connect
The IdP issues:
Access Token → expires in 30 minutes
Refresh Token → expires in 24 hours
When the user logs in again, you can configure the IdP to:
Invalidate all previous tokens
Issue new ones with fresh expiration times
Most IdPs (Okta, Auth0, Azure AD, Keycloak) support this pattern natively.
Using SAML 2.0
You can control AssertionLifetime (short-lived, e.g., 30 min)
The session cookie or IdP session index can persist for 24 hours
Logging in again invalidates both assertion and session
SAMPLE YAML
access_token:
expires_in: 1800 # 30 minutes
refresh_token:
expires_in: 86400 # 24 hours
on_login:
revoke_existing_tokens: true
This would be a HUGE blessing to members who use our Gospel Library to prepare talks, lessons, research the scriptures, add notes and links, etc. I can't possibly tell you how frustrating it is to write up a whole note in the Gospel Library and then when I go to SAVE my work, I'm told that I've been logged out. I've lost a LOT of inspired content as a result of this issue. I'd be SUPER grateful if you could implement a dual-authentication structure like the one defined above.
Robert Husted
rhusted@gmail.com