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

FIWARE.Question.Tech.Security.IDM-KeyRock.How to configure Keyrock to access a Restful API behind Wilma Proxy

    Details

      Description

      Created question in FIWARE Q/A platform on 11-02-2016 at 18:02
      Please, ANSWER this question AT https://ask.fiware.org/question/381/how-to-configure-keyrock-to-access-a-restful-api-behind-wilma-proxy/

      Question:
      How to configure Keyrock to access a Restful API behind Wilma Proxy

      Description:
      Hi, I'm developing an authentication/authorization scheme based on 3 Fiware Enablers: Keyrock IdM (v5.1.0), Wilma PEP Proxy (v4.4.1), AuthZForce (v4.4.1a). I'm using this scheme to protect another Fiware Enabler: POI Data Provider.

      I configured the components in order to allow a client to access a resource on the POI Data provider, sending a Restful http request to PEP Proxy that: verify the client's token; check his authorization to access the resource against AuthZForce and redirects the client to the resource if AuthZForce permit it.

      For example, if I want to access myResource on myMachine I have to send the following requst to myProxyMachine:

      curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource"

      It works fine as PEP Proxy redirects me to myResource on myMachine.

      But if I want to do a Restful request, with multiple parameters, for example:

      curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource?param1=1&param2=2"

      It doesn't work as AuthZForce deny the access to the resource.

      I think this is caused by Keyrock, because I created a permission for the client to do a GET on myResource, but this is not enough, because the URL of the request have other parameters and doesn't match with the rule.
      As the client can do multiple different requests, based on the parameters I just can't create multiple permissions on Keyrock.

      So, can anyone suggest how to create a permission on Keyrock to allow a client to GET myResource not regarding the other parameters? I didn't find how to achieve this in the documentation.

      Thanks in advance, Michele.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        15h 16m 1 Alvaro Alonso 12/Feb/16 10:19 AM
        In Progress In Progress Answered Answered
        1s 1 Alvaro Alonso 12/Feb/16 10:19 AM
        Answered Answered Closed Closed
        1s 1 Alvaro Alonso 12/Feb/16 10:19 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        backlogmanager Backlog Manager made changes -
        Summary FIWARE.Question.Tech.How to configure Keyrock to access a Restful API behind Wilma Proxy FIWARE.Question.Tech.Security.IDM-KeyRock.How to configure Keyrock to access a Restful API behind Wilma Proxy
        mev Manuel Escriche made changes -
        HD-Chapter Security [ 10841 ]
        mev Manuel Escriche made changes -
        HD-Enabler KeyRock [ 10889 ]
        Description
        Created question in FIWARE Q/A platform on 11-02-2016 at 18:02
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/381/how-to-configure-keyrock-to-access-a-restful-api-behind-wilma-proxy/


        +Question:+
        How to configure Keyrock to access a Restful API behind Wilma Proxy

        +Description:+
        Hi, I'm developing an authentication/authorization scheme based on 3 Fiware Enablers: Keyrock IdM (v5.1.0), Wilma PEP Proxy (v4.4.1), AuthZForce (v4.4.1a). I'm using this scheme to protect another Fiware Enabler: POI Data Provider.

        I configured the components in order to allow a client to access a resource on the POI Data provider, sending a Restful http request to PEP Proxy that: verify the client's token; check his authorization to access the resource against AuthZForce and redirects the client to the resource if AuthZForce permit it.

        For example, if I want to access myResource on myMachine I have to send the following requst to myProxyMachine:

        curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource"

        It works fine as PEP Proxy redirects me to myResource on myMachine.

        But if I want to do a Restful request, with multiple parameters, for example:

        curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource?param1=1&param2=2"

        It doesn't work as AuthZForce deny the access to the resource.

        I think this is caused by Keyrock, because I created a permission for the client to do a GET on myResource, but this is not enough, because the URL of the request have other parameters and doesn't match with the rule.
        As the client can do multiple different requests, based on the parameters I just can't create multiple permissions on Keyrock.

        So, can anyone suggest how to create a permission on Keyrock to allow a client to GET myResource not regarding the other parameters? I didn't find how to achieve this in the documentation.

        Thanks in advance, Michele.
        Created question in FIWARE Q/A platform on 11-02-2016 at 18:02
        {color: red}Please, ANSWER this question AT{color} https://ask.fiware.org/question/381/how-to-configure-keyrock-to-access-a-restful-api-behind-wilma-proxy/


        +Question:+
        How to configure Keyrock to access a Restful API behind Wilma Proxy

        +Description:+
        Hi, I'm developing an authentication/authorization scheme based on 3 Fiware Enablers: Keyrock IdM (v5.1.0), Wilma PEP Proxy (v4.4.1), AuthZForce (v4.4.1a). I'm using this scheme to protect another Fiware Enabler: POI Data Provider.

        I configured the components in order to allow a client to access a resource on the POI Data provider, sending a Restful http request to PEP Proxy that: verify the client's token; check his authorization to access the resource against AuthZForce and redirects the client to the resource if AuthZForce permit it.

        For example, if I want to access myResource on myMachine I have to send the following requst to myProxyMachine:

        curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource"

        It works fine as PEP Proxy redirects me to myResource on myMachine.

        But if I want to do a Restful request, with multiple parameters, for example:

        curl -H "X-Auth-Token: mytoken" -X GET "http://myProxyMachine:80/myResource?param1=1&param2=2"

        It doesn't work as AuthZForce deny the access to the resource.

        I think this is caused by Keyrock, because I created a permission for the client to do a GET on myResource, but this is not enough, because the URL of the request have other parameters and doesn't match with the rule.
        As the client can do multiple different requests, based on the parameters I just can't create multiple permissions on Keyrock.

        So, can anyone suggest how to create a permission on Keyrock to allow a client to GET myResource not regarding the other parameters? I didn't find how to achieve this in the documentation.

        Thanks in advance, Michele.
        backlogmanager Backlog Manager made changes -
        Summary [fiware-askbot] How to configure Keyrock to access a Restful API behind Wilma Proxy FIWARE.Question.Tech.How to configure Keyrock to access a Restful API behind Wilma Proxy
        aalonsog Alvaro Alonso made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        aalonsog Alvaro Alonso made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        aalonsog Alvaro Alonso made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        mev Manuel Escriche made changes -
        Assignee Alvaro Alonso [ aalonsog ]
        mev Manuel Escriche made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2016-02-11 19:05|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2016-02-11 19:05|CREATED monitor | # answers= 0, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: