Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Registration Page UX Revamp

Abierto
  • ¿Algo no está bien?
#203 1 comentario 0 reacciones 1 asignado Ver en GitHub

@Devayani1612 ya está trabajando en esto.

Desde el 13/8/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

enhancement OSS unruly

This is in regards to the UX for index.html (experienced at the web page https://store.rerum.io). On this page a code or project manager registers to use the API through Auth0 and are given a Refresh Token and an Access Token. These tokens are their key to use the RERUM API through https://store.rerum.io/v1/api/

Registered users can use this page to confirm their registration or get new tokens. This is important because Access Tokens expire regularly and if they are not programmatically refreshed they will need to be manually refreshed at this page.

The desired workflow is as follows.

  1. Start by logging in or signing up. This happens when the user clicks a button and they are sent off to Auth0 and come back with a ?code= or an ?error=

  2. If the user receives a valid ?code=, the page will inform the user they are authorized to use the RERUM API.

Image
  1. A valid code can be used to get a new Refresh Token. This is the most important token and users should be informed NOT TO LOSE IT. Refresh Tokens do not expire but are invalided if the user gets a different Refresh Token. Access Tokens that were produced using the old Refresh Token will be invalidated.
Image
  1. Getting a new Refresh Token automatically triggers getting a fresh Access Token. The Access Token is what the user will use to access the RERUM API. It is important that they do not lose it, but they can always get another one by providing their refresh token. Getting a new Access Token invalidates the old Access Token. Access Tokens expire every 30 days, there is no way for users to change that. If a user has a Refresh Token all they have to do is provide it, they do not have to log in.
Image

Users should not have to scroll around to find their ?code and tokens. Once the users have their tokens they should be able to download them to their machine in a plain text file. No changes to functionality are required and everything on the page is functioning as expected. This is just for an improved User Experience when coming to this page.

This should be done first as the top priority. Ideally it would be completed in one sprint, but two is still good.

  • A better result to registration where the user knows what happened, what the ?code= is, and how to get their tokens.
  • Update Authorization Status Checker
  • Update Access Token Verifier
  • Update Access Token Refresher
  • Update Refresh Token Getter
Lenguaje dominante
JavaScript
Estrellas
3
Forks
6
Merge medio
4 d 9 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CenterForDigitalHumanities/rerum_server_nodejs

Todos los issues de CenterForDigitalHumanities/rerum_server_nodejs

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.