Details
-
Type:
Monitor
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:
-
HD-Chapter:Security
-
HD-Enabler:AuthZForce
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:
- 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
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
3d 7h 33m | 1 | Cyril Dangerville | 13/Mar/17 7:37 PM | |||||
|
1d 4h 26m | 1 | Backlog Manager | 15/Mar/17 12:04 AM | |||||
|
18h | 1 | Backlog Manager | 15/Mar/17 6:04 PM |