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

FIWARE.Request.Tech.Security.IDM-KeyRock.issue

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None

      Description

      Hi,
      we have installed with docker an image of Keyrock Identity Management
      at the following address.

      http://185.23.171.56:5000/v3/auth/tokens <http://185.23.171.56:5000/v3/>

      We are trying to make a simple call from the API Examples
      http://docs.openstack.org/developer/keystone/api_curl_examples.html#admin-api-examples-using-curl

      and more specifically this method call.

      curl -i \
      -H "Content-Type: application/json" \
      -d '
      { "auth": {
      "identity": {
      "methods": ["password"],
      "password": {
      "user": {
      "name": "admin",
      "domain":

      { "id": "default" }

      ,
      "password": "adminpwd"
      }
      }
      }
      }
      }' \

      The response we are getting is,
      HTTP/1.1 500 Internal Server Error
      Vary: X-Auth-Token
      Content-Type: application/json
      Content-Length: 143
      Date: Wed, 14 Oct 2015 21:27:29 GMT

      {"error": {"message": "An unexpected error prevented the server from
      fulfilling your request.", "code": 500, "title": "Internal Server Error"}}

      Also we had a test with HTTP get at http://185.23.171.56:5000/v3
      and we get response OK (200)

      with the follow result

      {"version": {"status": "stable", "updated": "2013-03-06T00:00:00Z",
      "media-types": [

      {"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}

      ,

      {"base": "application/xml", "type": "application/vnd.openstack.identity-v3+xml"}

      ], "id": "v3.0",
      "links": [

      {"href": "http://185.23.171.56:5000/v3/", "rel": "self"}

      ]}}

      We think that this proves that we have successfully installed the KeyRock
      listening at 5000 but we cannot get any tokens.

      1.How we could we add users and get tokens from them through the API?
      2. Generally could you provide us a tutorial of testing the installation of
      the
      Keyrock IDM?

      Best Regards,

      Zacharias Papachristos,

      Beezon IoT Solutions

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help
      [Created via e-mail received from: zahos pap <zacpapac04@gmail.com>]

      1. horizon-idm.rar
        3 kB
        FW External User
      2. sign_up_error_Keyrock.rar
        8 kB
        FW External User
      3. signature.asc
        0.2 kB
        FW External User
      1. image.png
        36 kB
      2. image.png
        36 kB
      3. image.png
        36 kB
      4. image.png
        36 kB
      5. image.png
        36 kB
      6. image.png
        36 kB
      7. image.png
        36 kB
      8. image.png
        36 kB
      9. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      10. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      11. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      12. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      13. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      14. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      15. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      16. Screenshot from 2015-11-16 11_44_49.png
        69 kB
      17. Screenshot from 2015-11-16 11_44_49.png
        69 kB

        Activity

        Hide
        fw.ext.user FW External User added a comment -

        Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).

        Show
        fw.ext.user FW External User added a comment - Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).
        Hide
        fw.ext.user FW External User added a comment -

        Hi Zahos,

        I think the connection issue has definitely something to do with the node
        and is infrastructure. The fact that the error depends on the time frame
        really supports this. You should contact the Piraeus node administrators to
        fix it.

        About the SSL warning, don't worry too much about it. First of all, that
        trace is during the installation of the libraries, not the actual functing
        of Horizon. Furthermore, it's a very common warning to appear but has never
        been an actual issue. If you want to make sure it's not affecting the
        component, check this link
        https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning

        I'll take a look at the signup error. Seems like there is a path where the
        view doesn't return a response object, but I don't know why yet. Could you
        open a issue here https://github.com/ging/fiware-idm/issues so we can track
        it more easily? Email is not the best tool for this

        Best regards,
        Enrique

        Show
        fw.ext.user FW External User added a comment - Hi Zahos, I think the connection issue has definitely something to do with the node and is infrastructure. The fact that the error depends on the time frame really supports this. You should contact the Piraeus node administrators to fix it. About the SSL warning, don't worry too much about it. First of all, that trace is during the installation of the libraries, not the actual functing of Horizon. Furthermore, it's a very common warning to appear but has never been an actual issue. If you want to make sure it's not affecting the component, check this link https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning I'll take a look at the signup error. Seems like there is a path where the view doesn't return a response object, but I don't know why yet. Could you open a issue here https://github.com/ging/fiware-idm/issues so we can track it more easily? Email is not the best tool for this Best regards, Enrique
        Hide
        fw.ext.user FW External User added a comment -

        Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).

        Show
        fw.ext.user FW External User added a comment - Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).
        Hide
        fw.ext.user FW External User added a comment -

        Hi Enrique,

        I can confirm that problem comes only from FILAB Piraeus Node.
        I deployed the IDM-Keyrock on our VPS and we have no problem with
        connections,signup and timeouts from any terminal
        On FILAB the Keyrock can not be works well.

        I will request to open an issue about performance on Piraeus Node.

        Thanks at all,

        Zacharias,
        BeeZon IoT Solutions,

        On Mon, Nov 23, 2015 at 12:33 PM, Enrique Garcia Navalon <

        Show
        fw.ext.user FW External User added a comment - Hi Enrique, I can confirm that problem comes only from FILAB Piraeus Node. I deployed the IDM-Keyrock on our VPS and we have no problem with connections,signup and timeouts from any terminal On FILAB the Keyrock can not be works well. I will request to open an issue about performance on Piraeus Node. Thanks at all, Zacharias, BeeZon IoT Solutions, On Mon, Nov 23, 2015 at 12:33 PM, Enrique Garcia Navalon <
        Hide
        fw.ext.user FW External User added a comment -

        Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).

        Show
        fw.ext.user FW External User added a comment - Renamed attached file: 'Screenshot from 2015-11-16 11:44:49.png' to 'Screenshot from 2015-11-16 11_44_49.png' because it contained invalid character(s).

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: