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

FIWARE.Question.Tech.Security.AuthorizationPDP.PEP Proxy error: “AZF domain not created for application”

    Details

      Description

      Created question in FIWARE Q/A platform on 09-11-2016 at 18:11
      Please, ANSWER this question AT http://stackoverflow.com/questions/40513118/azf-domain-not-created-for-application-authzforce

      Question:
      “AZF domain not created for application” AuthZforce

      Description:
      I have an application that uses the KeyRock, PEP, PDP(AuthZForce).

      The security level 1 (authentication) with Keyrock and PEP are working, but when we try to use AuthZForce to check the authorization, I get the error message:

      AZF domain not created for application

      I have my user and my application that I created following the steps on the Fiware IdM User and Programmers Guide.

      I am also able to create domains as stated in the AuthZForce - Installation and Administration Guide but I don't know how to bind the Domain ID with user roles when creating them.

      So, how can I insert users/organizations/applications under a specific domain, and then have the security level 2?

      My config.js file:

      config.azf = {
      enabled: true,
      host: '192.168.99.100',
      port: 8080,
      path: '/authzforce/domains/',
      custom_policy: undefined
      };

      And my docker-compose.yml file is:

      authzforce:
      image: fiware/authzforce-ce-server:release-5.4.1
      hostname: authzforce
      container_name: authzforce
      ports:

      • "8080:8080"

      keyrock:
      image: fiware/idm:v5.4.0
      hostname: keyrock
      container_name: keyrock
      ports:

      • "5000:5000"
      • "8000:8000"

      pepproxy:
      build: Docker/fiware-pep-proxy
      hostname: pepproxy
      container_name: pepproxy
      ports:

      • 80:80
        links:
      • authzforce
      • keyrock

      This question is the same that AuthZForce Security Level 2: Basic Authorization error "AZF domain not created for application", but I get the same error, and my keyrock version is v5.4.0.

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

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

        Show
        backlogmanager Backlog Manager added a comment - 2016-11-09 21:05|CREATED monitor | # answers= 0, accepted answer= False
        Hide
        cdangerville Cyril Dangerville added a comment -

        The errors occurs in PEP so I notified the PEP Proxy owner (which I'm not). I also don't have enough reputation on Stackoverflow to be allowed to make comments to ask for more info.

        Show
        cdangerville Cyril Dangerville added a comment - The errors occurs in PEP so I notified the PEP Proxy owner (which I'm not). I also don't have enough reputation on Stackoverflow to be allowed to make comments to ask for more info.
        Hide
        cdangerville Cyril Dangerville added a comment -

        Alvaro (Idm/PEP owner) provided an answer on stackoverflow.

        Show
        cdangerville Cyril Dangerville added a comment - Alvaro (Idm/PEP owner) provided an answer on stackoverflow.
        Hide
        cdangerville Cyril Dangerville added a comment - - edited

        The original poster replied to Alvaro Alonso's comment, asking for clarification.
        I am re-assigning to the PEP Proxy owner since the error occurs in the PEP Proxy and the discussion involves mostly the PEP Proxy owner.

        Show
        cdangerville Cyril Dangerville added a comment - - edited The original poster replied to Alvaro Alonso 's comment, asking for clarification. I am re-assigning to the PEP Proxy owner since the error occurs in the PEP Proxy and the discussion involves mostly the PEP Proxy owner.

          People

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

            Dates

            • Created:
              Updated:
              Resolved: