Resolve CDMS 2.5 Login Issue

sekoukeita commented 1 year ago

The login issue on tribalCDMS_3.0 has been resolved

sekoukeita commented 1 year ago

Login issue fix

When trying to login, the user was receiving a 400 or 405 status code.

Solution

added the proxy.conf.json file in /src/appjsLegacy folder.
added proxyConfig property to the serve object in angular.json file.

Logout bug fix

When the user logged out, he was not redirected to the login page.

Solution

updated the routing in /src/app/login/components/logout/logout.components.ts

Page not found alert fix

After logging in, an alert message was displayed saying the page cannot be found.

Solution

In /src/appjsLegacy/main.ts, added the url 'http://localhost:4200/localhost:60681/index.html' to the list of urls to be ignored for the page not found alert.

Dataset and Project not showing after login (encountered by Tyler)

Once logged in, the dashboard could not display the list of projects and datasets.

Solution

I mistakenly commented out the dataset module in /src/appjsLegacy/main.ts, when removing the private files of Umatella. I have just uncommented those lines.

All those changes could be seen on this commit https://github.com/CRITFC/tribalCDMS-fe/commit/537b75b9e4587ed703c4c349a89bea4feb36926d#diff-451ec60cd93ba2cb3a26b1145f14ac65b3195e3805838c3ede204fc3d763be95

tylerstright commented 1 year ago

I went back through and updated my dev database with the SQL script, and was able to get that to work as expected. I am able to get beyond the login screen. However, I am not seeing the fixes you describe when I reach the landing page:

I cannot see datasets, projects, etc. Here's a few error messages from devtools:

Also, I don't believe some of the changes are correct for a different localhost setup. For example, for my cdms_dev 3.0 I am using localhost:90 and it appears my folder organization may be different than what I am seeing (e.g., 'http://localhost:4200/localhost:60681/index.html' in main.ts).

sekoukeita commented 1 year ago

Hi Tyler,

Sorry for what you're experiencing.

Did you get the latest version of tribalCDMS_3.0 front-end from the critfc repo, add your config.ts before building?

Sekou

On Thu, Jun 1, 2023, 4:34 PM Tyler @.***> wrote:

I went back through and updated my dev database with the SQL script, and was able to get that to work as expected. I am able to get beyond the login screen. However, I am not seeing the fixes you describe when I reach the landing page: [image: image] https://user-images.githubusercontent.com/42146185/242719026-84667619-96fa-4760-8f94-51b56ca3fd5a.png

I cannot see datasets, projects, etc. Here's a few error messages from devtools:

[image: image] https://user-images.githubusercontent.com/42146185/242720104-49dd3346-5c46-4db2-a715-55a194046481.png

Also, I don't believe some of the changes are correct for a different localhost setup. For example, for my cdms_dev 3.0 I am using localhost:90 and it appears my folder organization may be different than what I am seeing (e.g., 'http://localhost:4200/localhost:60681/index.html' in main.ts).

— Reply to this email directly, view it on GitHub https://github.com/CRITFC/Helpdesk/issues/70#issuecomment-1572740590, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHLAUTJ3UG4EK27YRQA3OQLXJD4FJANCNFSM6AAAAAAXBP33MI . You are receiving this because you commented.Message ID: @.***>

tylerstright commented 1 year ago

I am up to date on both tribalCDMS_3.0 branches and my config.ts file is in the appjsLegacy folder. I ran both 'npm update --save' and 'ng build' in Visual Studio Code. However, there appears to be a large number of error messages when I run 'ng build'. Did I forget an important step?

Thanks Tyler

sekoukeita commented 1 year ago

Hi Tyler,

Let's set up a meeting sometime tomorrow or Monday to take a look.

Sekou

JamminCRITFC commented 1 year ago

I had been experiencing issues logging into CRITFC's dev environment web UI. I think my problems were caused by using the incorrect Web.config file in the backend. Once I replaced it with the Web.config file supplied by Innovate, and modifying the "PasswordSalt" value to match what CRITFC's been using, user login works without issues.

However, when the wrong password is entered, instead of returning "Username or password were invalid" like our production environment, the dev site gets stuck on "Logging in...". It only returns the error message of "Failed to login Username is Inactive" with wrong usernames.

CRITFC / Helpdesk