Update help text on token management #9

New issue

Closed

opened 2025-11-17 12:02:00 +00:00 by a.wagner · 2 comments

a.wagner commented

2025-11-17 12:02:00 +00:00

Member

The token interface advises to email michael hanke in order to obtain a token:

I would suggest this text should point to the TRR379 docs instead. The docs will detail soon how to obtain a token using forgejo-based authentication.

The token interface advises to email michael hanke in order to obtain a token: ![image](/attachments/0128aee8-8e4f-4e78-bef6-e8209416d55f) I would suggest this text should point to the TRR379 docs instead. The docs will detail soon how to obtain a token using forgejo-based authentication.

image.png

49 KiB

jsheunis commented

2025-11-17 21:38:46 +00:00

Member

We can update these two config lines and then redeploy once we know what we want to say and point to exactly:

	`"token_info": "Please contact Michael Hanke at m.hanke@fz-juelich.de for credentials.",`
	`"token_info_url": "",`

It will be displayed as follows (I'm using markdown formatting in the link for illustration purposes only):
<token_info> [link](<token_info_url>)

+1 We can update these two config lines and then redeploy once we know what we want to say and point to exactly: https://hub.trr379.de/q02/pool.v0.trr379.de-ui/src/commit/748f6e9362d5c0acefd45cf40c3292eaf17ac1d0/config.json#L129-L130 It will be displayed as follows (I'm using markdown formatting in the link for illustration purposes only): `<token_info> [link](<token_info_url>)`

a.wagner referenced this issue from a pull request that will close it,

2026-01-29 14:23:16 +00:00

Point to docs for token #13