Openbravo Issue Tracking System - POS2 |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0056886 | POS2 | Core | public | 2024-10-24 14:00 | 2024-11-27 17:39 |
|
| Reporter | alostale | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | approved |
| Review Assigned To | |
| OBNetwork customer | No |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0056886: incorrect timeout to get OAuth tokens for client systems |
| Description | Client external systems configured with OAuth2 authentication perform a request to an authentication provider to obtain access tokens.
Currently the timeout for the request to obtain the token is hardcoded to 10 seconds. The mobile service that performs this request from POS (org.openbravo.mobile.core.externalsystem.HttpAuthorizationService) has a lower default timeout of 5s.
|
| Steps To Reproduce | 1 Configure a Client External System to use OAuth authentication
2 Subscribe that system to a fronetend event (ie. POS Login)
3 Trigger that event (ie. Log into POS) and ensure the authentication provider takes to responde more than 5s and less than 10s.
-> ERROR: the request is perceived as error from POS although the authentication provider responded correctly
|
| Proposed Solution | Workaround: it is possible to overwrite default timeout as system admin from the Mobile Services window for the org.openbravo.mobile.core.externalsystem.HttpAuthorizationService service |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-10-24 14:00 | alostale | New Issue | |
| 2024-10-24 14:00 | alostale | Assigned To | => Triage Platform Base |
| 2024-10-24 14:00 | alostale | OBNetwork customer | => No |
| 2024-10-24 14:00 | alostale | Triggers an Emergency Pack | => No |
| 2024-10-24 14:02 | alostale | Proposed Solution updated | |
| 2024-10-24 14:05 | hgbot | Merge Request Status | => open |
| 2024-10-24 14:05 | hgbot | Note Added: 0170898 | |
| 2024-10-24 14:10 | hgbot | Merge Request Status | open => approved |
| 2024-10-24 17:07 | martinsdan | Issue Monitored: martinsdan | |
| 2024-11-20 08:30 | hgbot | Note Added: 0172271 | |
| 2024-11-20 16:46 | hgbot | Note Added: 0172364 | |
| 2024-11-26 09:59 | hgbot | Note Added: 0172579 | |
| 2024-11-26 09:59 | hgbot | Note Added: 0172580 | |
| 2024-11-26 10:00 | hgbot | Note Added: 0172581 | |
| 2024-11-26 10:00 | hgbot | Note Added: 0172582 | |
| 2024-11-26 10:00 | hgbot | Note Added: 0172583 | |
| 2024-11-26 10:00 | hgbot | Resolution | open => fixed |
| 2024-11-26 10:00 | hgbot | Status | new => closed |
| 2024-11-26 10:00 | hgbot | Fixed in Version | => RR25Q1 |
| 2024-11-26 10:00 | hgbot | Note Added: 0172584 | |
| 2024-11-27 17:39 | hgbot | Note Added: 0172651 | |
|
Notes |
|
|
(0170898)
|
|
hgbot
|
|
2024-10-24 14:05
|
|
|
|
|
(0172271)
|
|
hgbot
|
|
2024-11-20 08:30
|
|
|
|
|
(0172364)
|
|
hgbot
|
|
2024-11-20 16:46
|
|
|
|
|
(0172579)
|
|
hgbot
|
|
2024-11-26 09:59
|
|
|
|
|
(0172580)
|
|
hgbot
|
|
2024-11-26 09:59
|
|
|
|
|
(0172581)
|
|
hgbot
|
|
2024-11-26 10:00
|
|
|
|
|
(0172582)
|
|
hgbot
|
|
2024-11-26 10:00
|
|
|
|
|
(0172583)
|
|
hgbot
|
|
2024-11-26 10:00
|
|
|
|
|
(0172584)
|
|
hgbot
|
|
2024-11-26 10:00
|
|
|
|
|
(0172651)
|
|
hgbot
|
|
2024-11-27 17:39
|
|
|