hotwax / launchpad Goto Github PK

Current behavior

If the user navigates to login from an app and then:

1. Goes to homepage
2. returns to login screen
3. enters login credentials
4. Redirected to app they navigated to launchpad from

Expected behavior

If the user exists the login flow and navigates to the Home Screen after which they return to the login page the redirect URL to the original app should be cleared from the state and the user should remain in launchpad.

Expected behavior

After logging out from the Moqui-based application, the user should be redirected to the login page or receive a confirmation message indicating a successful logout, without the page being stuck on "Processing."

Steps to reproduce the issue

Log out from the Launchpad.
Log in to any Moqui-based application.
Go to settings page and log out from the Moqui-based application.
Observe that the page remains stuck on "Processing."

Additional information

https://jam.dev/c/5b7765bf-bfcc-4db6-aa41-6d9fbeb8f343

Current behavior

When entering wrong oms name on the oms page, the user still moves to the login page and can try to login.

Expected behavior

If the entered name of oms is not correct the user should get a toast regarding same and should not be moved to the login page.

Steps to reproduce the issue

1. Open launchpad
2. Enter a wrong oms name
3. Click next, you can try to login into oms

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

Current behavior

Expected behavior

Currently, when users are redirected to the login page and their credentials are already pre-filled in the input fields, they receive an unnecessary toast notification prompting them to input credentials. This toast is confusing and redundant, as the credentials are already provided.

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

Current behavior

Currently, the "Enter" key is not functioning as expected when trying to input OMS information.

Expected behavior

After inputting the OMS information, the enter key should work and move the user to next page where credentials can be entered.

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

Current behavior

When using Launchpad, the login behavior is inconsistent when the application is opened in multiple tabs. If a user logs in to Launchpad in one tab, the other tab remains logged out and does not automatically log in, even though both tabs represent the same lauchpad instance.

Expected behavior

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

Current behavior

When the same user is logged in on both the app and Launchpad, the user needs to click the back button twice to return to Launchpad from the app.

Expected behavior

Clicking the back button once should return the user to Launchpad.

Steps to reproduce the issue

Log in to Launchpad with User A.
Log in to the app with the same User A.
Navigate within the app.
Attempt to return to Launchpad by clicking the back button.

Additional information

https://jam.dev/c/5e2618cb-4cfd-4de8-b54a-6dd68133a09c

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

Current behavior

On Clicking login button, the screen halts for some time and then the loader displays, results in confusion for the user and user might click the login button multiple times resulting in multiple api calls

Expected behavior

The loader should start instantly after clicking login button

Steps to reproduce the issue

• Go to launchpad login
• Fill in the required detaisl
• Click login

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

Current behavior

When attempting to log in to Launchpad after authentication token is expired, the pre-filled instance details on the login page are not being accepted and causing error.

Expected behavior

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

What is the motivation for adding/enhancing this feature?

Here is the Report -

20240221_OWASP_Top_10_2021_https_launchpad_hotwax_io_home.pdf

What are the acceptance criteria?

All the critical vulnerabilities should be fixed.

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Having a good README.md, It's easy to new developers to get familiar with the project

What are the acceptance criteria?

• About section
• Get Started section
• Contributing section

Can you complete this feature request by yourself?

• YES
• NO

Additional information

Refer other Readme.md files in similar projects

Current behavior

To improve user experience and prevent unnecessary redirection, we propose the implementation of a feature that ensures users are not redirected to the login page after a successful login when using the browser back button.

Expected behavior

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

What is the motivation for adding/enhancing this feature?

Currently our dashboard shows entry for the threshold management app. Instead we want to show entry of the newly developed "Atp" app in the dashboard.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

To enhance user experience and efficiency, we should prioritizing frequently used apps at the top of the list for quick selection. This feature will enable users to access their most commonly used apps more easily and reduce the time spent searching for them.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Currently, when a user logs in with new credentials, the existing credentials are not overwritten. The user is asked to resume or input new login .

What are the acceptance criteria?

When a user logs in with new credentials, the system should check if there is an existing credential for the same user. If there is, the system should override the existing credential with the new credential.

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

When users initiate the logout process in SSO-enabled applications that use SAML, they are redirected to the login page of the application after logging out.

What are the acceptance criteria?

When beginning the logout process in applications that support SAML SSO, users should be directed to the OMS instance page.

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Currently. The Launchpad login page is missing the Go to apps button which needs to be added for easy navigation.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

would like to propose an enhancement to the user interface by adding a spinner inside the logout button. Currently, when users click the logout button, it can be unclear whether their request is being processed. By integrating a spinner directly inside the button, users will have a visual cue that their action is in progress. This small but impactful change can significantly improve the user experience.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

Expected behavior

The toast message should accurately convey that the user account is blocked or disabled, providing clear information to the user about the reason for denied access.

Steps to reproduce the issue

Block or disable a user account within the application.
Attempt to access the application using the blocked or disabled user account credentials.
Observe the toast message displayed upon denied access.

Environment details

• App version: v1.6.0
• Testing Environment: UAT

Additional information

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

Current behavior

We should make the instance chip red when instance is not found. There should be no scenario where user is not allowed to proceed to login page. Attached video where that is happening.

https://jam.dev/c/4545ecc6-f589-4dea-9942-1230ff81f293

Clicking app card or button should open the app in a new tab

Right now every element that needs to be animated on the hover of a card has to get animation curves applied to it manually and updating animation curves later will require updating all instances of its usage across various elements. There should be a way to centrally manage animation timings related to card hover.

What is the motivation for adding/enhancing this feature?

In our current system, when a user has an active session in an app and tries to login in another app, they are faced with an alert, the alert message is unclear. We need to improve the clarity and user-friendliness of this message.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

This new category will help to organize the User Management application and make it easier for users to find the functionality they need.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

Current behavior

Despite successfully logging out, when the user attempts to log in an application, it continues to make multiple futile attempts to authenticate using the expired token.

Expected behavior

Following a user logout, the application should recognize the invalidated token and immediately prompt the user for fresh login credentials.

Steps to reproduce the issue

Can you handle fixing this bug by yourself?

• YES
• NO

Environment details

• Browser:
• OS:
• Code Version:

Additional information

What is the motivation for adding/enhancing this feature?

Common users will not want to navigate to the users app to view their user details. Instead the launchpad user card should have an option to jump straight to the user's profile.

What is the motivation for adding/enhancing this feature?

Add the entry of the Company app in the launchpad dashboard.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Currently, our system does not adequately handle log out requests when the system is experiencing downtime or has been terminated. To improve user experience and provide appropriate feedback during such scenarios, we propose enhancing the log out API to gracefully handle situations where the system is unavailable.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

This will help the user in having a clarity, that in which app user will be redirected after login.

What are the acceptance criteria?

• Show the app's name on the UI

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Currently, accessing the Order Management System (OMS) requires users to navigate through multiple pages, which can be time-consuming and inefficient.

Implement a dedicated section or button on the Home page that provides seamless access to the OMS for users who are already logged in.

What are the acceptance criteria?

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

What is the motivation for adding/enhancing this feature?

Currently, the system does not prompt users to change their passwords after the password expiration period has elapsed.

What are the acceptance criteria?

Implement a feature that prompts users to change their passwords after the expiration period has passed. This is crucial for security purposes, ensuring that users regularly update their passwords and maintain the integrity of their accounts.

• ...

Can you complete this feature request by yourself?

• YES
• NO

Additional information

make the whole app. don't need styling

Touch devices shouldn't have hover css because they cannot differentiate between a touch, click and hover.

Note

Also when user logged in the app and clicks back button of browser, user is logged in again instead of redirecting user to Launchpad.
https://jam.dev/c/d8b8fa14-b334-4e6c-8d54-213dd1ebb2b2

Current behavior

When Launchpad is logged in with one user and another user tries to log in to the app, an error is displayed for 1-2 seconds. The error message shown is "Login Failed". Additionally, a toast message appears on the UI stating "Something went wrong while login. Please contact administrator".

Expected behavior

The app should allow the new user (User B) to log in without displaying any error messages.

Steps to reproduce the issue

Log in to Launchpad with User A.
Attempt to log in to the app with User B.
Observe the error messages.

Additional information

https://jam.dev/c/282f656a-0727-4cbc-95c0-3f094827cfde