about summary refs log tree commit diff
path: root/test/python/test_groups.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-06 17:17:39 +0000
committerPjotr <wrk@bosa.lan>2026-11-06 17:17:39 +0000
commitc39dd5440e29b7d6abcc602009c863a2c11ae1f7 (patch)
tree41841d87f9c19d448c3b77edb866128ce853e6f2 /test/python/test_groups.py
parent5210ca7139b8670d8620c4924351605ae0550d5d (diff)
downloadgenenetwork4-c39dd5440e29b7d6abcc602009c863a2c11ae1f7.tar.gz
gn-auth-stub: --expires-in, document the public-data-only token
A stub token had a fixed 24h lifetime, and nothing said what an
ungranted one can reach. Both matter for the case that is not a test
run: handing a caller or an agent a long-lived token that may only read
public data. An ungranted stub token already is exactly that -- the
restriction lives in the authorisation lookup genenetwork4 consults for
anything not public, not in the token's scope -- so only the lifetime
was missing.

* scripts/gn-auth-stub.py (duration): new helper, "30d"/"24h"/"60m"/s.
(sign): take expires_in instead of a hard-coded 86400.
(main): --expires-in, defaulting to 24h as before; docstring says what
an ungranted token can reach and why the key's fixity makes a month-long
token safe.
* README.md (Tests): the public-data-only token, what stays visible
(dataset metadata), the --expires-in example and the iss/port coupling.
Diffstat (limited to 'test/python/test_groups.py')
0 files changed, 0 insertions, 0 deletions