[Backlogmanager] [FIWARE-JIRA] (HELP-8843) [fiware-stackoverflow] authentication on spagobi using keyrock

José Ignacio Carretero Guarde (JIRA) jira-help-desk at jira.fiware.org
Mon May 29 11:56:00 CEST 2017


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

José Ignacio Carretero Guarde reassigned HELP-8843:
---------------------------------------------------

    Assignee: Davide Zerbetto

> [fiware-stackoverflow] authentication on spagobi using keyrock
> --------------------------------------------------------------
>
>                 Key: HELP-8843
>                 URL: https://jira.fiware.org/browse/HELP-8843
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Davide Zerbetto
>              Labels: fiware, oauth2, spagobi
>
> Created question in FIWARE Q/A platform on 24-03-2016 at 18:03
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/36206819/authentication-on-spagobi-using-keyrock
> +Question:+
> authentication on spagobi using keyrock
> +Description:+
> We're having troubles authenticating on SpagoBI using KeyRock as authentication provider. We followed the guide here: 
> http://spagobi.readthedocs.org/en/latest/admin/README/index.html
> The redirection to KeyRock works, but after we enter the user credentials there is an error which says: 
> {"state": "None", "error": "invalid_redirect_uri"} (HTTP 400)
> The configuration page in KeyRock looks like this:
> keyrock screenshot
> We've simply copied client id, secret and the other parameters required in the oauth2.config.properties.
> Note: the default urls for the public instance of KeyRock were wrong, we had to add /oauth2 to make them work, probably they were prepared for a previous version of KeyRock. 
> EDIT 30-03-2016
> Some more information:
> we're using the public instance of KeyRock  
> we're using a private
> instance of SpagoBI deployed on our servers using the Docker
> container available in docker hub 
> This is the the content of our
> oauth2.config.properties 
> CLIENT_ID = 123456
> SECRET = 123456
> REDIRECT_URI = http://192.168.196.15:8080/SpagoBI/servlet/AdapterHTTP?PAGE=LoginPage&NEW_SESSION=TRUE
> TOKENS_URL = https://account.lab.fiware.org/api/v1/tokens.json
> APPLICATIONS_BASE_URL = https://account.lab.fiware.org/oauth2/applications/
> AUTHORIZE_BASE_URL = https://account.lab.fiware.org/oauth2/authorize
> GET_ACCESS_TOKEN_URL = https://account.lab.fiware.org/oauth2/token
> GET_USER_INFO_URL = https://account.lab.fiware.org/oauth2/user
> APPLICATION_NAME = SpagoBI
> ADMIN_EMAIL = fiwarelab at email
> ADMIN_PASSWORD = fiwarelab at password
> We've add the /oauth2/ part in the addresses, otherwhise we would get a 404 error on the redirect to KeyRock.



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