[Backlogmanager] [FIWARE-JIRA] (HELP-16873) [fiware-askbot] Fiware-Biz end to end testing help needed

Fernando Lopez (JIRA) jira-help-desk at jira.fiware.org
Mon Aug 17 10:10:00 CEST 2020


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

Fernando Lopez reassigned HELP-16873:
-------------------------------------

    Assignee: Francisco de la Vega

> [fiware-askbot] Fiware-Biz end to end testing help needed
> ---------------------------------------------------------
>
>                 Key: HELP-16873
>                 URL: https://jira.fiware.org/browse/HELP-16873
>             Project: Help-Desk
>          Issue Type: Monitor
>            Reporter: Backlog Manager
>            Assignee: Francisco de la Vega
>              Labels: IdM, biz-ecosystem
>
> Created question in FIWARE Q/A platform on 03-08-2020 at 13:08
> {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/1183/fiware-biz-end-to-end-testing-help-needed/
> +Question:+
> Fiware-Biz end to end testing help needed
> +Description:+
> I am attempting to set up a docker deployment of the FIWARE-BIZ ecosystem as shown in guide  as well as do the end-to-end testing as shown at the end of the installation and administration document 
> The first problem I think I've run into was the fact that the docker deployment guide specifies no idm and the end to end testing guide states that an idm and a seller role account are necessary. To that end I have added a fiware/idm:7.6.0 container to the end of the biz ecosystem docker-compose.yml
> keyrock:
>         image: fiware/idm:7.6.0
>         containername: fiware-keyrock
>         hostname: keyrock
>         networks:
>             main:
>                 aliases:
>                     - idm.docker
>                 ipv4address: 172.18.0.9
>         dependson:
>             - mysql
>         ports:
>             - "3000:3000"
>             - "443:443"
>         environment:
>             - DEBUG=idm:*
>             - IDMDBHOST=mysql
>             - IDMHOST=http://localhost:3000
>             - IDMPORT=3000
>             # Development use only
>             # Use Docker Secrets for Sensitive Data
>             - IDMDBPASS=my-secret-pw
>             - IDMDBUSER=root
>             - IDMADMINUSER=admin
>             - IDMADMINEMAIL=admin at test.com
>             - IDMADMINPASS=1234
>     mysql:
>         image: mysql:5.7
>         restart: always
>         volumes:
>             - ./mysql-data:/var/lib/mysql
>         networks:
>             main:
>         environment:
>             - MYSQLROOTPASSWORD=my-secret-pw
>             - MYSQLDATABASE=RSS
> as well as changed the proxy setting 
> - BAELPOAUTH2SERVER=http://idm.docker:8000
> to
> - BAELPOAUTH2SERVER=http://localhost:3000
> Now when I click sign-in on the fiware tmforum marketplace (proxy) page, I am taken to the keyrock sign-in where I can log in with the credentials specified in the docker-compose.yml but I am at a loss on how to make it take me back to the tmforum marketplace (proxy) page despite the fact that I think I've sucessfully made a seller account.
> EDIT : I've also changed the :
> - BAELPOAUTH2CLIENTID=71644c8b-c413-440e-9699-6d2f44db5623 
> - BAELPOAUTH2CLIENTSECRET=c15d82aa-b217-4148-a6da-1eacf3d3a989 
> - BAELPOAUTH2_CALLBACK=http://localhost:8004/auth/fiware/callback 
> The client ID and secret are now identical to the ones in the example app I made in keyrock with the help of the built in tutorial, and the callback is now on localhost. I am now after logging in taken to a Authorization page for "First App" but after I click authorize I I get status code 400 "invalid client".
> Is there any way to set up a biz ecosystem instance in docker and do the end to end testing as described in the guide above ?
> In case it wasn't bountifully clear I am a complete beginner with fiware and I apologise if I've broken any rules with this post or asked a dumb question.



--
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