Skip to content

1231 refine the auth0 login process #1250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 10 commits into from

Conversation

Ezequiel-Valencia
Copy link
Contributor

No description provided.

Add the endpoint for forgetting your password.
Allow a HTTP connection when the "isHTTP" property is set to true.
Added the ability to control the URL utilized by the client created to interact with quarkus. Before it assumed that Quarkus and the legacy API where on the same host, but now that doesn't have to be the case. It still makes that assumption if other options aren't provided.
Attempted to incorporate a dynamic path prefix to the quarkus API, but it was unnecessary since no matter if there's an ingress or not the path will always have the prefix /api/v1.
Change the audience for the JWT token to vcellapi because although the domain may be incorrect, the protocol used for that domain is the same for local development, thus one less thing to take care of.
Popup a GUI telling the enduser about the redirection of the browser. Initial creation still needs refinement.
The function already contained within AdminDB existed, but was not an available function to classes external to its module, so I've relaxed the restrictions and made it public.
@Ezequiel-Valencia Ezequiel-Valencia self-assigned this May 21, 2024
@Ezequiel-Valencia Ezequiel-Valencia linked an issue May 21, 2024 that may be closed by this pull request
13 tasks
@jcschaff
Copy link
Member

@AvocadoMoon please review this PR and decide what to do with it, sorry that my review was requested 6 months ago. Now this branch has many conflicts and would have to be rebased. - the underlying issue #1231 is closed, does that mean this is obsolete?

@Ezequiel-Valencia
Copy link
Contributor Author

Reviewed and it seems that the critical changes:

  • Changing the JWT token's audience
  • Allowing password reset through email
  • Dynamic login GUI pop-up

Is already implemented within the master branch. The assumption is that certain commits from this branch has been cherry picked and placed within master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Refine the Auth0 login process
2 participants