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

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

    Details

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

      Description

      Web Browser: Google Chrome version 38.0.2125.104
      Operating System: OSX version 10.9.3
      Description:

      In a previous issue, titled ‘Account’s issues to access filab’, we
      explained we couldn’t access filab using a gmail’s account. Thus, we had to
      sign in using another account: pablofm@gmail.com. Then we were logged as
      Pablo.

      When we received a confirmation email to the hotmail’s account we logged in
      using that hotmail’s account. We clicked on Mashup button and when the page
      reloaded we were, again, logged as Pablo without closing session or
      changing users.

      Here are the details about the users and account used.

      1. Pablo - pablofm@gmail.com
      2. Wirecloud - wirecloud.test.ulpgc@hotmail.com

      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        118d 4h 15m 1 Alvaro Alonso 26/Feb/15 4:55 PM
        In Progress In Progress Closed Closed
        35s 1 Alvaro Alonso 26/Feb/15 4:56 PM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        mev Manuel Escriche made changes -
        HD-Enabler KeyRock [ 10889 ]
        HD-Chapter Security [ 10841 ]
        mev Manuel Escriche made changes -
        Summary FIWARE.Request.Lab.Security.IDM-KeyRock.Sessionissues FIWARE.Request.Tech.Security.IDM-KeyRock.Sessionissues
        aalonsog Alvaro Alonso made changes -
        Summary FIWARE.Request.Lab.Session issues FIWARE.Request.Lab.Security.IDM-KeyRock.Sessionissues
        backlogmanager Backlog Manager made changes -
        Summary [Fiware-lab-help] [Wirecloud][General] Session issues FIWARE.Request.Lab.Session issues
        aalonsog Alvaro Alonso made changes -
        Resolution Done [ 10000 ]
        Status In Progress [ 3 ] Closed [ 6 ]
        Hide
        aalonsog Alvaro Alonso added a comment -

        It's so strange... anyway as we are going to update the release next week it will be fixed.

        Show
        aalonsog Alvaro Alonso added a comment - It's so strange... anyway as we are going to update the release next week it will be fixed.
        aalonsog Alvaro Alonso made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        pablo.fernandez Pablo Fernandez Moniz added a comment -

        Ok. We think the explanation given helps understanding why this happens.

        Thank you.

        Show
        pablo.fernandez Pablo Fernandez Moniz added a comment - Ok. We think the explanation given helps understanding why this happens. Thank you.
        aarranz Álvaro Arranz made changes -
        Assignee Álvaro Arranz García [ aarranz ] Álvaro Alonso [ aalonsog ]
        Hide
        aarranz Álvaro Arranz added a comment - - edited

        Although the description of this issue uses the Mashup portal, I think this problem is more related to the IdM SSO architecture (so I'm going to reassign this issue to the IdM team).

        Currently, each portal has his own session management. The Mashup portal closes the user session when the user sign outs directly from the Mashup portal or from another of the global portals (there is a mechanism for signalling this event). If you didn't close your session before following the link provided by the confirmation email, the old user session was never closed in the Mashup portal. This had also happened to other FIWARE Lab's portals as they use the same scheme.

        Show
        aarranz Álvaro Arranz added a comment - - edited Although the description of this issue uses the Mashup portal, I think this problem is more related to the IdM SSO architecture (so I'm going to reassign this issue to the IdM team). Currently, each portal has his own session management. The Mashup portal closes the user session when the user sign outs directly from the Mashup portal or from another of the global portals (there is a mechanism for signalling this event). If you didn't close your session before following the link provided by the confirmation email, the old user session was never closed in the Mashup portal. This had also happened to other FIWARE Lab's portals as they use the same scheme.
        mev Manuel Escriche made changes -
        Workflow FW eRequest Workflow [ 18217 ] FW extRequest Workflow-II [ 20264 ]
        Issue Type eRequest [ 10101 ] extRequest [ 10104 ]
        FI-WARE Environment FI-LAB [ 10100 ]
        mev Manuel Escriche made changes -
        Component/s FIWARE-TECH-HELP [ 10278 ]
        aarranz Álvaro Arranz made changes -
        Field Original Value New Value
        Assignee Álvaro Arranz García [ aarranz ]
        pablo.fernandez Pablo Fernandez Moniz created issue -

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            pablo.fernandez Pablo Fernandez Moniz
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: