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

[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 http://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.

      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

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        backlogmanager Backlog Manager made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        cdangerville Cyril Dangerville made changes -
        Assignee Cyril Dangerville [ cyril.dangerville ] Alvaro Alonso [ aalonsog ]
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        cdangerville Cyril Dangerville made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        fla Fernando Lopez made changes -
        Assignee Cyril Dangerville [ cyril.dangerville ]
        fla Fernando Lopez made changes -
        HD-Enabler AuthZForce [ 10887 ]
        Description
        Created question in FIWARE Q/A platform on 10-03-2017 at 09:03
        {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/42714175/fiware-authzforce-error-azf-domain-not-created-for-application


        +Question:+
        Fiware AuthZForce error: &quot;AZF domain not created for application&quot;

        +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 &lt;applicationID&gt;


        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:

        # ACCESS CONTROL GE
        ACCESS_CONTROL_URL = 'http://azfcontainer:8080&#39;
        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.

        This question is the same that “AZF domain not created for application” AuthZforce, but my problem persists even with the shown AuthZForce GE Configuration.
        Created question in FIWARE Q/A platform on 10-03-2017 at 09:03
        {color: red}Please, ANSWER this question AT{color} http://stackoverflow.com/questions/42714175/fiware-authzforce-error-azf-domain-not-created-for-application


        +Question:+
        Fiware AuthZForce error: &quot;AZF domain not created for application&quot;

        +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 &lt;applicationID&gt;


        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:

        # ACCESS CONTROL GE
        ACCESS_CONTROL_URL = 'http://azfcontainer:8080&#39;
        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.

        This question is the same that “AZF domain not created for application” AuthZforce, but my problem persists even with the shown AuthZForce GE Configuration.
        HD-Chapter Security [ 10841 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          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: