You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adjust the naming to refer to end date rather than expire for peers. Hopefully
that will reduce the confusion about the difference between the date that the
local contact puts as hard end date and the individual account access expire
value. The latter needs at least annual renewal and the users can handle that
themselves until end date.
logger.info("%s begin for %s"% (op_name, client_id))
92
92
93
93
# IMPORTANT: single line here to avoid breaking javascript inlining
94
-
expire_help="For security reasons peer accounts should be closed when no longer required. Expire is used to limit account access time for that purpose, and you can always extend it later if needed. For courses and workshops a few weeks or months should usually suffice, while projects and long-term collaboration often extend to months or years. Peer accounts still need to be renewed at least annually, but the peer users can do so themselves without your repeated explicit acceptance, as long as it does not exceed your provided expire date."
94
+
expire_help="For security reasons peer accounts should be closed when no longer required. End date is used to limit account access time for that purpose, and you can always extend it later if needed. For courses and workshops a few weeks or months should usually suffice, while projects and long-term collaboration often extend to months or years. Peer accounts still need to be renewed at least annually, but the peer users can do so themselves without your repeated explicit acceptance, as long as it does not exceed your provided end date."
95
95
96
96
# jquery support for tablesorter and confirmation on delete
97
97
# table initially sorted by col. 5 (kind), then 0 (name)
0 commit comments