Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0014679 | Openbravo ERP | A. Platform | public | 2010-09-23 15:13 | 2022-02-01 08:08 |
|
Reporter | plujan | |
Assigned To | Triage Platform Base | |
Priority | urgent | Severity | major | Reproducibility | have not tried |
Status | new | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | main | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0014679: DE011 A canceled subscription allows me to use modules with an expired license |
Description | A canceled subscription allows me to use modules with an expired license |
Steps To Reproduce | 1. Use an active instance with a professional subscription. The subscription will expire in day 3.
2. Quick Start module is installed. The module's license expires in day 2.
3. DAY 1: Everything work as usual
4. DAY 2: QS expires. You receive a message and you cannot login.
4.1. Option A: You do nothing. You cannot use the system.
4.2. Option B: You disable QS. You can use the system but you cannot use QS
5. DAY 3: Subscription expires. As SysAdmin, you cancel the license.
5.1. If Option A: You are able to use the system again. Quick Start is available
5.2. If Option B: You can enable Quick Start. Quick Start is available.
|
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-09-23 15:13 | plujan | New Issue | |
2010-09-23 15:13 | plujan | Assigned To | => alostale |
2010-09-27 08:59 | alostale | Status | new => scheduled |
2011-11-18 17:17 | johnfandl | Note Added: 0042993 | |
2012-03-23 12:13 | alostale | Note Added: 0046678 | |
2012-03-23 12:13 | alostale | Status | scheduled => closed |
2012-03-23 12:13 | alostale | Resolution | open => no change required |
2012-03-23 12:46 | plujan | Note Added: 0046682 | |
2012-03-23 12:46 | plujan | Status | closed => new |
2012-03-23 12:46 | plujan | Resolution | no change required => open |
2012-03-28 17:27 | alostale | Note Added: 0046847 | |
2012-03-28 17:27 | alostale | Type | defect => design defect |
2017-04-10 14:37 | alostale | Assigned To | alostale => platform |
2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
Notes |
|
|
This sounds like it is working as designed. Per 11. of trial license FAQ (http://wiki.openbravo.com/wiki/Trial_FAQ#FAQs_for_Free_Trial_of_Openbravo_3_Professional_Edition [^]):
Canceling a Basic or Professional Edition subscription allows you to continue using the system in its current state, including its premium features and previously installed commercial modules--but with no update services, no ability to install new commercial modules, and no ability to add additional users.
This is a benefit offered only to customers, to support the “no vendor lock-in” philosophy of Openbravo and to ensure that the decision to acquire commercial module does not put our customers in a position to be forced to renew their subscription.
The thing to ensure is that after cancellation, these restrictions are in place:
- no ability to update commercial modules
- no ability to install new commercial modules
- no ability to add additional users
- concurrent user control continues to be enforced |
|
|
|
|
|
(0046682)
|
plujan
|
2012-03-23 12:46
|
|
I'm sorry but I disagree. "Working as designed" is not enough argument to close the issue.
If you consider the inconsistency I reported does not worth to fix, reject it as "won't fix", but the issue stands as valid one for me. |
|
|
|
After discussing it with plujan we agreed the design defect is for the time lapse between module expiration and license expiration. During this time, module cannot be used but after it, it is possible to cancel and use.
Needs to be discussed to apply a proper solution: might be to allow to cancel not only on license expiration but also on any module expiration. |
|