Closed sripathikrishnan closed 4 years ago
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
spam bot
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
spam bot
Thanks for all your contributions! This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Description
When I create an application token, the token is visible for a very short period of time - 5 seconds or so. It needs considerable dexterity to copy it before it disappears.
Also, it is also on the top right of the screen, and very easy to miss. It took me several attempts to find out the token was actually getting created. I feel that is the underlying reason for the confusion in https://github.com/SUSE/Portus/issues/2179
This problem is more severe when using OAuth2 providers, because using application tokens is the only way to run the docker login command.
Suggestion
The token is displayed using
$alert.$show
method. This autohides the alert by default after 5 seconds. Perhaps we should change the timeout to 60s, or perhaps set autohide=false?Steps to reproduce
docker login
command. I expect to manually dismiss the alert.Deployment information
This behaviour is independent of the deployment method. But for the record, I used docker-compose, along with google oauth2 configured.
Configuration:
This is a javascript issue, and I don't believe it depends on the configuration. Neverthless, here is the configuration:
Portus version: Version: 2.5.0-dev@a1b9f2ebfeb84680a9dcd5629195e4c52815735c. This is based on the published docker image
opensuse/portus@sha256:a3e3324c59929fbb0949c806300d0645d271eacdd30f4bfbc77e7f938540ce9f