[FOLIO-2830] Cannot login via UI to vagrant box folio/testing Created: 08/Oct/20 Updated: 09/Oct/20 Resolved: 09/Oct/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | DevOps: Sprint 99 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
With the VM folio/testing v5.0.0-20201007.5086, cannot login via the frontend as diku_admin. Doing login via curl to the backend is successful. On initial load of the UI, this message in console:
GET http://localhost:9130/saml/check
400 Bad Request
Invalid URL path requested /saml/check
Then when try to login, this message in console:
POST http://localhost:9130/bl-users/login?expandPermissions=true&fullPermissions=true
400 Bad Request
Invalid URL path requested /bl-users/login
|
| Comments |
| Comment by David Crossley [ 08/Oct/20 ] |
|
Viachaslau Khandramai Can you recall when you were were last able to login sucessfully? (As i do not use this box often.) |
| Comment by Viachaslau Khandramai (Inactive) [ 08/Oct/20 ] |
|
Hi David Crossley |
| Comment by Viachaslau Khandramai (Inactive) [ 08/Oct/20 ] |
|
Now I see the following in the Web Inspector: Invalid URL path requested /bl-users/login |
| Comment by Siarhei Hrabko [ 08/Oct/20 ] |
|
David Crossley the last working box version is = "5.0.0-20200927.5034" |
| Comment by Wayne Schneider [ 08/Oct/20 ] |
|
Initial investigation shows that some modules seem to be working just fine, while Okapi refuses to proxy to others (mod-users-bl, mod-circulation, mod-inventory). Okapi log shows: 2020-10-08T15:17:38,696 INFO ProxyContext 351531/bl-users REQ 0:0:0:0:0:0:0:1%0:49982 diku POST /bl-users/login mod-authtoken-2.7.0-SNAPSHOT.78 mod-users-bl-6.2.0-SNAPSHOT.94 2020-10-08T15:17:38,698 INFO ProxyContext 351531/bl-users RES 202 2288us mod-authtoken-2.7.0-SNAPSHOT.78 http://10.0.2.15:9133/bl-users/login 2020-10-08T15:17:38,717 INFO DockerModuleHandle mod-pubsub-1.4.0-SNAPSHOT.107 15:17:38.716 [vert.x-eventloop-thread-0] INFO LogUtil [3227622eqId] 10.0.2.15:40244 POST /bl-users/login null HTTP_1_1 400 42 -1 tid=null Bad Request Invalid URL path requested /bl-users/login 2020-10-08T15:17:38,718 INFO ProxyContext 351531/bl-users RES 400 19952us mod-users-bl-6.2.0-SNAPSHOT.94 http://10.0.2.15:9149/bl-users/login |
| Comment by Wayne Schneider [ 08/Oct/20 ] |
|
The issue appears to be related to restoring the state of module deployment after restarting Okapi (using Okapi for Docker deployment). This is what http://localhost:9130/_/discovery/modules/mod-users-bl-6.2.0-SNAPSHOT.94 shows:
[ {
"instId" : "731dd313-0efc-40be-ac6c-b18213805074",
"srvcId" : "mod-users-bl-6.2.0-SNAPSHOT.94",
"nodeId" : "10.0.2.15",
"url" : "http://10.0.2.15:9149",
"descriptor" : {
"dockerImage" : "folioci/mod-users-bl:6.2.0-SNAPSHOT.94",
"dockerPull" : true,
"env" : [ {
"name" : "DB_MAXPOOLSIZE",
"value" : "5"
}, {
"name" : "DB_USERNAME",
"value" : "folio_admin"
}, {
"name" : "DB_PORT",
"value" : "5432"
}, {
"name" : "JAVA_OPTIONS",
"value" : "-XX:MaxRAMPercentage=66.0"
}, {
"name" : "DB_HOST",
"value" : "10.0.2.15"
}, {
"name" : "DB_DATABASE",
"value" : "okapi_modules"
}, {
"name" : "DB_PASSWORD",
"value" : "folio_admin"
} ],
"dockerArgs" : {
"HostConfig" : {
"Memory" : 357913941,
"PortBindings" : {
"8081/tcp" : [ {
"HostPort" : "9144"
} ]
}
}
}
}
} ]
Note that the Docker HostPort is 9144, while the url points to port 9149. |
| Comment by Wayne Schneider [ 08/Oct/20 ] |
|
Same behavior with the folio/testing-backend Vagrant box |
| Comment by Wayne Schneider [ 08/Oct/20 ] |
|
And folio/snapshot, so it begins to look like a general issue. |
| Comment by Wayne Schneider [ 08/Oct/20 ] |
|
Raised
|
| Comment by David Crossley [ 08/Oct/20 ] |
|
A clarification. I said in the ticket Description that i could login via the backend. That was because i was using the /authn/login endpoint. |
| Comment by Wayne Schneider [ 09/Oct/20 ] |
|
With release of Okapi v4.1.7, this appears to be resolved (thanks, Adam Dickmeiss!) |