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

FIWARE.Request.Tech.Demo accounts for a workshop / trial vs community accounts.

    Details

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

      Description

      Dear Alvaro and all,

      coming from the ticket https://jira.fiware.org/browse/HELP-7078,
      I would like to clarify the following.

      In HELP-7078, it was discussed about activating community accounts on Hannover node.
      This should work fine now, however as our workshop is on weekend, we will have no operator to activate the requested community accounts in real time.

      However what I did not know that recently there are also trial accounts, which allow activation launch of instances just by the requesting user as self-service without administrative support. However, these resources are given from the Spain2 node without option for other locations.

      Therefore I see now the following ways to achieve our goal, namely secure enough available resources during the workshop. We need to evaluate ASAP what is the best way.

      Clarification still needed:

      • can Spain2 guarantee for 50 trial accounts for us?
      • or, is it possible to let trial accounts go to Hannover?

      If the options above are not feasible:

      • or, is it better (and safer) to go for community accounts at Hannover and create all of them beforehand (this would require also email accounts instead of letting workshop participants apply themselves for test account).

      In any case, is there an engineer with enough knowledge to provide a script to create accounts not one by one via interface but by an admin from a csv file containing a minimum required data inputs for valid accounts? (in future, this will be good not only for workshops, but for adding organisations). If this is not securely possible on short term, this should be a separate ticket.

      kind regards
      Peter

        Activity

        Hide
        fla Fernando Lopez added a comment -

        Dear Peter,

        The normal actuation in these cases is that the users create their own trial accounts throuth the account.lab.fiware.org portal. I think that it is the best option, no bottle necks.

        Currently there is no problem with the creation of Trial Accounts in the FIWARE Lab but they are created by default in Spain2 node (it is how it was defined). Nevertheless, There is a possiblity to allow users to access to other regions appart from Spain2. It is something that have to be manage by hand once that we have the list of these trial users. You can send them to me and I can do it by hand.

        The automatic creation of users is something that was disabled in the past for secure reason. Could be internally manage in the tool but I have to check this availability with the FIWARE Secure team.

        Kind regards,
        Fernando

        Show
        fla Fernando Lopez added a comment - Dear Peter, The normal actuation in these cases is that the users create their own trial accounts throuth the account.lab.fiware.org portal. I think that it is the best option, no bottle necks. Currently there is no problem with the creation of Trial Accounts in the FIWARE Lab but they are created by default in Spain2 node (it is how it was defined). Nevertheless, There is a possiblity to allow users to access to other regions appart from Spain2. It is something that have to be manage by hand once that we have the list of these trial users. You can send them to me and I can do it by hand. The automatic creation of users is something that was disabled in the past for secure reason. Could be internally manage in the tool but I have to check this availability with the FIWARE Secure team. Kind regards, Fernando
        Hide
        peter Peter Muryshkin added a comment -

        Hi, Fernando,

        thanks for this update! I will come back to you. Please check with the secure team, after all it is about having the possibility to reduce time efforts for the internal FIWARE teams to create (or remove) a bunch of test account like for the workshop we plan.

        kind regards
        Peter

        Show
        peter Peter Muryshkin added a comment - Hi, Fernando, thanks for this update! I will come back to you. Please check with the secure team, after all it is about having the possibility to reduce time efforts for the internal FIWARE teams to create (or remove) a bunch of test account like for the workshop we plan. kind regards Peter
        Hide
        fla Fernando Lopez added a comment -

        To remove users, there is a specific FIWARE Operation tools that was developed to remove the expired users.

        Show
        fla Fernando Lopez added a comment - To remove users, there is a specific FIWARE Operation tools that was developed to remove the expired users.
        Hide
        peter Peter Muryshkin added a comment -

        is it public?

        Show
        peter Peter Muryshkin added a comment - is it public?
        Hide
        fla Fernando Lopez added a comment - - edited

        NOOOO, you can imagine The reason of it is to avoid security issues to delete any users in the platform. This is an administrative tool (FIWARE Operation tool) that it is available only for FIWARE Lab infrastructure owner. In fact, currently, it is used only by the Master Node.

        Show
        fla Fernando Lopez added a comment - - edited NOOOO, you can imagine The reason of it is to avoid security issues to delete any users in the platform. This is an administrative tool (FIWARE Operation tool) that it is available only for FIWARE Lab infrastructure owner. In fact, currently, it is used only by the Master Node.

          People

          • Assignee:
            fla Fernando Lopez
            Reporter:
            peter Peter Muryshkin
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: