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

FIWARE.Question.Tech.Security.IDM-KeyRock.FIWare KeyRock: How to prevent fiware labs data being created when a new user registers

    Details

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

      Description

      Created question in FIWARE Q/A platform on 30-04-2016 at 19:04
      Please, ANSWER this question AT http://stackoverflow.com/questions/36958289/fiware-keyrock-how-to-prevent-fiware-labs-data-being-created-when-a-new-user-re

      Question:
      FIWare KeyRock: How to prevent fiware labs data being created when a new user registers

      Description:
      We want to use the FIWARE IdM, both Keystone and Horizon.
      We have installed both using the latest docker container on the docker hub.
      When a new user signs up:

      a 'cloud organisation' is created.
      By default, the 'provider' and 'purchaser' roles are present
      and the 'Store' application is assigned to the user (although i cannot verify this).

      However this does not make any sense for our local installation.

      How can we prevent Horizon from creating the cloud organisation upon user sign-up?
      How can we assign a default application authorization upon user sign-up?

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2016-04-30 21:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-04-30 21:05|CREATED monitor | # answers= 0, accepted answer= False

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: