Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
HD-Chapter:Security
-
HD-Enabler:KeyRock
Description
Web Browser: Mozilla Firefox, v. 33 ; Google Chrome, v. 38.0.2125.104
Operating System: Windows 8
User id: storedata.test.ulpgc@gmail.com
Description
In a computer in which two Fi-Lab accounts are used with some frequency,
session errors could be found so, in fact, you can use two accounts at the
same time. The pattern detected is that you can use an account in
Cloud-CKAN-Account areas and another one in Store-Mashup areas.
This issue would be quite annoying if you acquire an offering with CKAN
resources at the Store with the first account and you try to check for your
resource in CKAN, because the second account is active for CKAN.
That means you can see your recently acquired CKAN resource only if the
same resource was acquired for the other account, although you acquired
your CKAN resource without any problem.
How to replicate
You need to use two accounts with some frequency. Log off from one account
[in this testing example, a personal “mxmeater” account] and log in the
second one [in this testing example, our testing “
storedata.test.ulpgc@gmail.com” account]
We could use “storedata.test.ulpgc” normally at the Mashup and Store areas,
but when you try to change from that areas to Cloud, CKAN or Account, our
user changed from “storedata.test.ulpgc” to “mxmeater”, and you can see
several information about “mxmeater” account (example, its Cloud machines).
If you want to return to the Store/Mashup areas, the user account changed
again from “mxmeater” to “storedata.test.ulpgc”.
See attached pictures 1-2-3-4-5 in order to clarify this point:
Now go to the Store and purchase a CKAN resource which you have already
acquired in the second account. You will see you can search for your
resource … in the second account.
The pictures 6-7 can explain you better this topic.
Finally, try to acquire another CKAN offering. This second CKAN offering
must not be acquired for the second account.
You will see [attached picture 8] that the purchasing process will finish
fine, but the following error appears when you try to look for your data in
CKAN, because the second account has no access to that data.
_______________________________________________
Fiware-lab-help mailing list
Fiware-lab-help@lists.fi-ware.org
https://lists.fi-ware.org/listinfo/fiware-lab-help
Issue Links
- is cloned by
-
HELP-2308 FIWARE.Request.Tech.Apps.Store.LackConsistenceUserInformation
- Closed
Activity
Field | Original Value | New Value |
---|---|---|
Assignee | Eliot Salant [ esalant ] |
Status | Open [ 1 ] | Answered [ 10104 ] |
Component/s | FIWARE-TECH-HELP [ 10278 ] |
Workflow | FW eRequest Workflow [ 17290 ] | FW extRequest Workflow-II [ 20406 ] |
Issue Type | eRequest [ 10101 ] | extRequest [ 10104 ] |
FI-WARE Environment | FI-LAB [ 10100 ] |
Assignee | Eliot Salant [ esalant ] | Kenneth Nagin [ knagin ] |
Assignee | Kenneth Nagin [ knagin ] | Alvaro Alonso [ aalonsog ] |
Resolution | Done [ 10000 ] | |
Status | Answered [ 10104 ] | Closed [ 6 ] |
Summary | [Fiware-lab-help] [Fi-lab] Lack of consistence in user account information between the different areas included in FILAB | FIWARE.Request.Lab.Lack of consistence in user account information between the different areas included in FILAB |
Summary | FIWARE.Request.Lab.Lack of consistence in user account information between the different areas included in FILAB | FIWARE.Request.Lab.Security.IDM-KeyRock.Lackofconsistence |
Summary | FIWARE.Request.Lab.Security.IDM-KeyRock.Lackofconsistence | FIWARE.Request.Tech.Security.IDM-KeyRock.Lackofconsistence |
HD-Enabler | KeyRock [ 10889 ] | |
HD-Chapter | Security [ 10841 ] |
Fix Version/s | 2021 [ 12600 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
21h 28m | 1 | Manuel Escriche | 24/Oct/14 10:18 AM | |||||
|
166d 5h 23m | 1 | Alvaro Alonso | 08/Apr/15 3:42 PM |