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

[fiware-stackoverflow] FIWARE IDM Obtaining X-Auth-Token in Angular app

    Details

      Description

      Created question in FIWARE Q/A platform on 30-09-2020 at 19:09
      Please, ANSWER this question AT https://stackoverflow.com/questions/64142882/fiware-idm-obtaining-x-auth-token-in-angular-app

      Question:
      FIWARE IDM Obtaining X-Auth-Token in Angular app

      Description:
      I'm using the FIWARE IDM 7.8.1, by the request from a project, I have to use the X-Auth-Token.
      At the client-side, the app is written in Angular, so when I try to send a request for an access token using a method with a password, I'm not able to read X-Subject-Token from the header in the response. The only attributes that are accessible through the Angular app are content-length, content-type, and cache-control.
      I know that this kind of problem is resolved by exposing the x-token from the server-side, but I'm not sure how I can manage changes on the FIWARE IDM, or there is something that maybe I'm missing in the Angular request?

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        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 ]
        fla Fernando Lopez made changes -
        HD-Enabler KeyRock [ 10889 ]
        Description
        Created question in FIWARE Q/A platform on 30-09-2020 at 19:09
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/64142882/fiware-idm-obtaining-x-auth-token-in-angular-app


        +Question:+
        FIWARE IDM Obtaining X-Auth-Token in Angular app

        +Description:+
        I'm using the FIWARE IDM 7.8.1, by the request from a project, I have to use the X-Auth-Token.
        At the client-side, the app is written in Angular, so when I try to send a request for an access token using a method with a password, I'm not able to read X-Subject-Token from the header in the response. The only attributes that are accessible through the Angular app are content-length, content-type, and cache-control.
        I know that this kind of problem is resolved by exposing the x-token from the server-side, but I'm not sure how I can manage changes on the FIWARE IDM, or there is something that maybe I'm missing in the Angular request?
        Created question in FIWARE Q/A platform on 30-09-2020 at 19:09
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/64142882/fiware-idm-obtaining-x-auth-token-in-angular-app


        +Question:+
        FIWARE IDM Obtaining X-Auth-Token in Angular app

        +Description:+
        I'm using the FIWARE IDM 7.8.1, by the request from a project, I have to use the X-Auth-Token.
        At the client-side, the app is written in Angular, so when I try to send a request for an access token using a method with a password, I'm not able to read X-Subject-Token from the header in the response. The only attributes that are accessible through the Angular app are content-length, content-type, and cache-control.
        I know that this kind of problem is resolved by exposing the x-token from the server-side, but I'm not sure how I can manage changes on the FIWARE IDM, or there is something that maybe I'm missing in the Angular request?
        fla Fernando Lopez made changes -
        Assignee Alvaro Alonso [ aalonsog ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        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: