Skip to content
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

Auth0 Browser Pop-Up #1375

Closed
3 tasks
AvocadoMoon opened this issue Nov 5, 2024 · 1 comment · Fixed by #1388 or #1395
Closed
3 tasks

Auth0 Browser Pop-Up #1375

AvocadoMoon opened this issue Nov 5, 2024 · 1 comment · Fixed by #1388 or #1395
Assignees
Labels
Type: enhancement enhance existing feature

Comments

@AvocadoMoon
Copy link
Contributor

AvocadoMoon commented Nov 5, 2024

Problem

The browser pop-up is distracting to the end user, and is not required to gain focus if they are already logged in.

Potential Solutions

  • Create a HTTP client within the app that can store cookies, and make all the requests the browser can do

    • Browser logic is extremely complicated and attempting to allow GUI interaction for when users need to initiate authentication for the first time would also be difficult. Then comes the problem of how to store cookies securely on the client device. | Attempt To Store Cookies
  • Keep everything the same, but have the browser pop-up be silent so tabs accumulate but never gain focus. Or have the java app gain focus back from the browser.

    • No method so far seems to allow for silent browser interaction or focus gain.
  • Store the ID and refresh token in a secure manner

    • After the user logs in save the tokens grabbed, and once the refresh token expires restart the entire authentication process again. | KeyRing Library
  • Change the authentication flow such that it browser interaction isn't required

    • The other flows don't seem to support streamlined methods without having the client application store some secret which is not possible in our case.

Best Solution

The best solution seems to be storing the credentials in a secure manner on the native machine, and refreshing when needed. The OS native method for storing secrets securely can propose some issues, however, if storage doesn't work the application can just go through the sign-in process all over again.

Tasks

  • Create a credential store class whose purpose is to store and retrieve secrets
  • Integrate the class in a non-intrusive manner to the current login procedure
  • Create diagram which reflects the entire login process
@AvocadoMoon AvocadoMoon added the Type: enhancement enhance existing feature label Nov 5, 2024
@AvocadoMoon AvocadoMoon self-assigned this Nov 5, 2024
@AvocadoMoon AvocadoMoon moved this to Pool in vcell development Nov 5, 2024
@AvocadoMoon AvocadoMoon moved this from Pool to Active in vcell development Nov 8, 2024
@AvocadoMoon AvocadoMoon linked a pull request Nov 21, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from Active to Done in vcell development Nov 21, 2024
@AvocadoMoon AvocadoMoon reopened this Nov 21, 2024
@AvocadoMoon
Copy link
Contributor Author

Documentation is available, however, the problem still has not been solved.

@jcschaff jcschaff linked a pull request Dec 6, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: enhancement enhance existing feature
Projects
Status: Done
1 participant