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

[fiware-stackoverflow] Fiware AuthZForce error: "AZF domain not created for application"

    Details

      Description

      Created question in FIWARE Q/A platform on 10-03-2017 at 09:03
      Please, ANSWER this question AT https://stackoverflow.com/questions/42714175/fiware-authzforce-error-azf-domain-not-created-for-application

      Question:
      Fiware AuthZForce error: "AZF domain not created for application"

      Description:
      I'm trying to protect Orion Context Broker using KeyRock idm, Wilma PEP-Proxy and AuthZForce PDP over Docker. For now, level 1 security works well and I can deny access to non logged users, but I get this error on Wilma when trying to add level 2.

      AZF domain not created for application <applicationID>

      Here it is my azf configuration in Wilma's config.js file:

      config.azf = {
      enabled: true,
      protocol: 'http',
      host: 'azfcontainer',
      port: 8080,
      custom_policy: undefined
      };

      And this is how I set the access control configuration on KeyRock:

      1. ACCESS CONTROL GE
        ACCESS_CONTROL_URL = 'http://azfcontainer:8080'
        ACCESS_CONTROL_MAGIC_KEY = None

      I have created the custom policies on Keyrock, but AuthZForce logs don't show any request from KeyRock or Wilma, so no domain is created on the PDP. I have checked that all containers can see and reach each other and that all ports are up. I may be missing some configuration.

      These are the versions I'm using:

      keyrock=5.4.1
      wilma=5.4
      autzforce=6.0.0/5.4.1

      This question is the same that “AZF domain not created for application” AuthZforce, but my problem persists even with the shown AuthZForce GE Configuration.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2h 56m 1 Backlog Manager 22/May/17 6:06 PM
        In Progress In Progress Closed Closed
        3h 1 Backlog Manager 22/May/17 9:06 PM

          People

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

            Dates

            • Created:
              Updated:
              Resolved: