Closed ctunited15 closed 1 year ago
There is definitely some issue in this space still on v2.x.x branch @maurycupitt.
We do not allow empty fields 👍 , but invalid login information does not provide any user feedback or errors?
Initial root cause is this line:
const loggedIn = await requestService.loginViaRest();
as this does not return true/false upon success/failed login - true implies the request was made successfully, not that it received an acceptable response.
This is an example of the use of internal REST APIs, which we should avoid.
We should move towards https://www.npmjs.com/package/@sonatype/nexus-iq-api-client
Turns out that because this call is to an internal /rest
API, it uses COOKIE if it is there and avoids the actual credentials enters.
Looks like #267 now becomes more important...
Resolved now in v2.x.x branch.
Clicking the login, gives the message "Login Successful", but when saving, it errors out. It is easy to test by entering the wrong username / pw.
The problem is that I am already logged in and the cookie is still there. It should be invalidated.