[Backlogmanager] [FIWARE-JIRA] (HELP-14153) [fiware-stackoverflow] Domain not found: AZF domain not created for application

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Wed Sep 12 09:21:00 CEST 2018


     [ https://jira.fiware.org/browse/HELP-14153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-14153:
----------------------------------
    Description: 
Created question in FIWARE Q/A platform on 18-05-2018 at 15:05
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50412682/domain-not-found-azf-domain-not-created-for-application


+Question:+
Domain not found: AZF domain not created for application

+Description:+
I got this error while trying to configure level 2 authentication using idm,pep-proxy and pdp.
I am using latest version of authzforce,idm,pep-proxy but this error still persists.
  config.azf = {
    enabled: true,
    protocol: 'http',
    host: 'localhost',
    port: 8080,
    custom_policy: undefined // use undefined to default policy checks (HTTP verb + path).
};
par of config that is relevant.

As i understand idm connected with authzforce should auto create domains, but for some reason that is not case.

I have tried with different versions, read similar issues on stack but problem still persist.Any advice or maybe point what i am doing wrong would be really helpful.
Thanks


  was:

Created question in FIWARE Q/A platform on 18-05-2018 at 15:05
{color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50412682/domain-not-found-azf-domain-not-created-for-application


+Question:+
Domain not found: AZF domain not created for application

+Description:+
I got this error while trying to configure level 2 authentication using idm,pep-proxy and pdp.
I am using latest version of authzforce,idm,pep-proxy but this error still persists.
  config.azf = {
    enabled: true,
    protocol: 'http',
    host: 'localhost',
    port: 8080,
    custom_policy: undefined // use undefined to default policy checks (HTTP verb + path).
};
par of config that is relevant.

As i understand idm connected with authzforce should auto create domains, but for some reason that is not case.

I have tried with different versions, read similar issues on stack but problem still persist.Any advice or maybe point what i am doing wrong would be really helpful.
Thanks


     HD-Enabler: Wilma

> [fiware-stackoverflow] Domain not found: AZF domain not created for application
> -------------------------------------------------------------------------------
>
>                 Key: HELP-14153
>                 URL: https://jira.fiware.org/browse/HELP-14153
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Alvaro Alonso
>              Labels: authzforce, fiware
>
> Created question in FIWARE Q/A platform on 18-05-2018 at 15:05
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/50412682/domain-not-found-azf-domain-not-created-for-application
> +Question:+
> Domain not found: AZF domain not created for application
> +Description:+
> I got this error while trying to configure level 2 authentication using idm,pep-proxy and pdp.
> I am using latest version of authzforce,idm,pep-proxy but this error still persists.
>   config.azf = {
>     enabled: true,
>     protocol: 'http',
>     host: 'localhost',
>     port: 8080,
>     custom_policy: undefined // use undefined to default policy checks (HTTP verb + path).
> };
> par of config that is relevant.
> As i understand idm connected with authzforce should auto create domains, but for some reason that is not case.
> I have tried with different versions, read similar issues on stack but problem still persist.Any advice or maybe point what i am doing wrong would be really helpful.
> Thanks



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)


More information about the Backlogmanager mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy