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

FIWARE.Request.Tech.Security.IDM-KeyRock.General Support #447: URGENT! Keyrock login fails after update

        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

          Hi,

          an applicant has opened us a ticket describing errors on KeyRock after
          today Filab update. It is quite urgent as it is preventing a scheduled
          update of their product, which is in production stage.

          This is the entire message:

          *Logging in with my user account (matias@lumegames.com
          <matias@lumegames.com>) stopped working after the update today. This
          happens with both OAuth2 sequence with external service and logging in
          directly to account.lab.fiware.org <http://account.lab.fiware.org/>. I get
          redirected to front page which responds with error message. Removing
          cookies allows me to try logging in again, but with the same result.*

          THIS IS PREVENTING A SCHEDULED UPDATE TO OUR PRODUCT!!!

          Thanks in advance,

          Marc Palau
          i2CAT - Software Engineering Group

          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-creatifi-coaching@lists.fiware.org) instead of the old one.
          _______________________________________________
          Fiware-creatifi-coaching mailing list
          Fiware-creatifi-coaching@lists.fiware.org
          https://lists.fiware.org/listinfo/fiware-creatifi-coaching
          [Created via e-mail received from: Marc Palau <marc.palau@i2cat.net>]

            Issue Links

            relates to

            extRequest - Request from external stakeholder received in the help desk HELC-1373 FIWARE.Request.Coach.CreatiFI.General Support #447: URGENT! Keyrock login fails after update

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              gcossu Giuseppe Cossu added a comment -

              Hello,
              I've just sent your request to the KeyRock GE owner.

              Regards,
              Giuseppe

              Show
              gcossu Giuseppe Cossu added a comment - Hello, I've just sent your request to the KeyRock GE owner. Regards, Giuseppe
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Hi,

              it should be fixed. Could you confirm?

              Show
              aalonsog Alvaro Alonso added a comment - Hi, it should be fixed. Could you confirm?
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment -

              Dear,
              I check with the accelerator and then I come back to you
              BR

              Show
              silviocretti Silvio Cretti added a comment - Dear, I check with the accelerator and then I come back to you BR
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment -

              Dear,
              the accelerator sent me:

              ****************
              Hi,
              the applicant has tried and unfortunately it does not work. I have asked
              him to clean the cache of its browser and try again.
              He has also added some information: "I noticed the server sets 4 cookies. I
              tried removing them one by one and it seems that cookie "sessionid" alone
              causes the error. The cookie has 1114 bytes of data, which suggests that
              the authentication was successful and the error happens only after that."
              Thanks,

              Show
              silviocretti Silvio Cretti added a comment - Dear, the accelerator sent me: **************** Hi, the applicant has tried and unfortunately it does not work. I have asked him to clean the cache of its browser and try again. He has also added some information: "I noticed the server sets 4 cookies. I tried removing them one by one and it seems that cookie "sessionid" alone causes the error. The cookie has 1114 bytes of data, which suggests that the authentication was successful and the error happens only after that." Thanks,
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Hi Silvio, I'm sorry but I cannot reproduce the error... all our accounts are working and we have not receive any other similar report. I don't know how we can try to reproduce it...

              Show
              aalonsog Alvaro Alonso added a comment - Hi Silvio, I'm sorry but I cannot reproduce the error... all our accounts are working and we have not receive any other similar report. I don't know how we can try to reproduce it...
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Hi Silvio, good news. We received the report of other user with the same issue and we have finally found the reason. It is fixed now!

              Show
              aalonsog Alvaro Alonso added a comment - Hi Silvio, good news. We received the report of other user with the same issue and we have finally found the reason. It is fixed now!

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved: