Minor Description
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
EXAMPLE:
lockout count = 7
obfuscated user runs same query 7 times and gets results returned each time.
The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client.
EXAMPLE:
lockout count = 7
obfuscated user runs same query 7 times and gets results returned each time.
The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Web Client doesn't cancel query when obfuscated user | Web Client doesn't cancel query when user receives lockout message |
| Description |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
The resolution is to have the Web Client "cancel" the query when the lockout message is received from the CRC. |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
This issue is to track any changes needed on the Web Client side. Another issue will be submitted for tracking changes needed on the server side. |
| Summary | Web Client doesn't cancel query when user receives lockout message | Query continues to run after user receives lockout message |
| Description |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
This issue is to track any changes needed on the Web Client side. Another issue will be submitted for tracking changes needed on the server side. |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
This issue is to track any changes needed on the Web Client side. Another issue will be submitted for tracking changes needed on the server side. EXAMPLE: lockout count = 7 obfuscated user runs same query 7 times and gets results returned each time. The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client. |
| Key |
|
|
| Workflow | Web Client Issues Workflow [ 11671 ] | i2b2 Issues Workflow [ 11672 ] |
| Project | i2b2 Web Client [ 10033 ] | i2b2 Core Software [ 10034 ] |
| Description |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
This issue is to track any changes needed on the Web Client side. Another issue will be submitted for tracking changes needed on the server side. EXAMPLE: lockout count = 7 obfuscated user runs same query 7 times and gets results returned each time. The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client. |
When an obfuscated exceeds the allowed number of times they can repeat a query they will be "locked out" from running another query. When they receive the message telling them they have been locked out, the system should cancel the query they are trying to run. However, when they click on OK the Web Client continues to run the query.
EXAMPLE: lockout count = 7 obfuscated user runs same query 7 times and gets results returned each time. The next time (8th time) the obfuscated user runs the query, the status of Cancelled will display in Show Query Status. However, when you look in the qt_query_master table the query doesn't have a DELETE_DATE or DELETE_FLAG which indicates the query was not cancelled as indicated in the Web Client. |
| Assignee | Mike Mendis [ mem61 ] |
| Attachment | obfscUser-lockOut-qryError.png [ 10936 ] |
| Attachment | obfscUser-lockOut-qryError.png [ 10936 ] |
| Attachment | obfscUser-lockOut-qryCancelled-2.png [ 10938 ] |
| Fix Version/s | 1.7.12 [ 10901 ] |
| Status | New [ 10000 ] | Open [ 1 ] |
| Assignee | Mike Mendis [ mem61 ] | Jeffrey Klann [ jklann ] |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Fix Version/s | 1.7.13 [ 10902 ] | |
| Fix Version/s | 1.7.12 [ 10901 ] |
| Fix Version/s | TBD [ 11005 ] | |
| Fix Version/s | 1.7.13 [ 10902 ] |
| Fix Version/s | 1.7.13 [ 10902 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Assignee | Jeffrey Klann [ jklann ] | Reeta Metta [ rm302 ] |
| Status | In Progress [ 3 ] | Ready to Test [ 10001 ] |
| Status | Ready to Test [ 10001 ] | Testing [ 10002 ] |
| Comment | [ on the 7th attempt , user will receive ERROR msg ] |
When user runs the query after lock out(7th attempt), query will be cancelled with ERROR msg and previous query shows ERROR status. see screenshot
| Attachment | screenshot-1.png [ 11445 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Testing [ 10002 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
CORE-282fix. Need to test.