Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-3427

FIWARE.Request.Tech.Security.IDM-KeyRock.CommonCloudOrganization

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Blocker
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Hi,

      since i had no response for almost 10 days now, i forward this email to
      your communication channel for getting back answer on the specific issues
      we face concerning fiware lab.

      BRs,
      Dimitris Karantonis
      BeeZon Smart Software IoT Solution

      ---------- Forwarded message ----------
      From: Dimitris Karantonis <dkarantonis@gmail.com>
      Date: Tue, Jun 16, 2015 at 12:25 AM
      Subject: Fiware lab - issue with multiple members accessing common cloud
      organization
      To: tech@fractals-fp7.com, John Sokianos <ysokianos@gmail.com>, zahos pap <
      zacpapac04@gmail.com>, super mario <mariosprotos@gmail.com>, Carmen Perea <
      carmen.perea@atos.net>, communityaccount@fiware.org

      Hi,

      i am Dimitris Karantonis, member of the BeeZon Smart Software IoT Solution,
      qualified for the fractals accelerator (BeeZon : Real Time Continuous
      Apiary Monitoring System).

      I have created an account on fiware lab named "dkarantonis". Then, i
      requested an account upgrade and after some days, my account finally
      upgraded to "community".
      I then created an organization (via fiware lab) named "BeeZon Smart
      Software IoT Solution Cloud" and added / authorized as members / owners the
      other 3 members of the development team (fiware account names are
      "ysokianos", "zacpapac04","mariosprotos"). So far all good. When i switch
      to "BeeZon Smart Software IoT Solution Cloud" session from the top right
      corner menu, i am able to access the cloud menu as expected. I have also
      added a vm instance named "BeeZon-iot-orion-instance".

      I have 2 really important questions though, that block our development team
      to co-operate and share the created instance.

      1) The rest of the team members need to upgrade their account in order to
      access the cloud menu. Why is this? Shouldn't they use the Beezon cloud
      created via my account, since i authorized them to use it?
      2) The one of the team members (named "zacpapac04") has already upgraded
      his account and is able to access the cloud menu. When he switches to the
      "BeeZon Smart Software IoT Solution Cloud" session and navigate to the
      cloud menu, he is not able to see "BeeZon-iot-orion-instance" as expected,
      rather he sees his own cloud instance "zacpapac04 cloud" (created from iw
      own account)... Seems like, no matter what session you switch to (via top
      right corner), when navigating to the cloud menu, you only have access to
      the organization created by your own fiware account.

      Could you please advice on how to proceed?
      Our goal is to create on cloud to be used from all team members.
      Is there something we are missing or setting up incorrectly?

      BRs,
      Dimitris Karantonis
      BeeZon Smart Software IoT Solution

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

      [Created via e-mail received from: Dimitris Karantonis <dkarantonis@gmail.com>]

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        5h 27m 1 Alvaro Alonso 25/Jun/15 2:47 PM
        In Progress In Progress Answered Answered
        1s 1 Alvaro Alonso 25/Jun/15 2:47 PM
        Answered Answered Closed Closed
        1s 1 Alvaro Alonso 25/Jun/15 2:47 PM

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: