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

FIWARE.Request.Tech.Security.IDM-KeyRock.OAuth2 sequence intermittently fails

        Details

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

          Description

          Hi,

          an applicant has sent us an error he has detected using KeyRock.

          "This is mostly a nuisance, since it can be worked around easily, but
          occasionally the OAuth2 sequence fails, with the following message "Error:
          Unable to retrieve application." at the bottom of the page at
          https://account.lab.fiware.org/auth/login/?next=/idm/

          (Going back to our web application and redoing the authentication fixes
          this.)"

          Thanks!

          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-1243 FIWARE.Request.Coach.CreatiFI.General Support #425: Keyrock - OAuth2 sequence intermittently fails

            • Major - Major loss of function.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment -

              Dear,
              I suggest you to forward the issue to the FIWARE IdM experts: Joaquín Salvachúa or Álvaro Alonso
              Thanks

              Show
              silviocretti Silvio Cretti added a comment - Dear, I suggest you to forward the issue to the FIWARE IdM experts: Joaquín Salvachúa or Álvaro Alonso Thanks
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Hi,

              many thanks for the report. I have created an issue in the component project: SEC-789

              BR

              Show
              aalonsog Alvaro Alonso added a comment - Hi, many thanks for the report. I have created an issue in the component project: SEC-789 BR
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment -

              Dear,
              I re-open the ticket in order to wait for a feedback. Even if the isses is not so critical, we have a sort of "contractual" duty with CreatiFI projects that assumes that if a ticket is submitted by a CreatiFI applicant it should be answered here.

              So, let me know when the issue will be fixed.
              Thanks a lot for your understanding

              BR

              Show
              silviocretti Silvio Cretti added a comment - Dear, I re-open the ticket in order to wait for a feedback. Even if the isses is not so critical, we have a sort of "contractual" duty with CreatiFI projects that assumes that if a ticket is submitted by a CreatiFI applicant it should be answered here. So, let me know when the issue will be fixed. Thanks a lot for your understanding BR
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Hi Silvio,

              I've assigned the bug to the Sprint 5.3.1. In my opinion is better to close this ticket because the question has been attended and processed. It has generated other ticket that belongs to the GE backlog component (SEC-789) and that will take time to be resolved.

              BR

              Show
              aalonsog Alvaro Alonso added a comment - Hi Silvio, I've assigned the bug to the Sprint 5.3.1. In my opinion is better to close this ticket because the question has been attended and processed. It has generated other ticket that belongs to the GE backlog component (SEC-789) and that will take time to be resolved. BR
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment -

              Hi Alvaro,
              I understand but on the other side, if we close the ticket, how can the applicant be notified? He cannot see "private tickets".
              So we could also close it but then we should find another way to inform the applicant.
              Do you have any idea?
              silvio

              Show
              silviocretti Silvio Cretti added a comment - Hi Alvaro, I understand but on the other side, if we close the ticket, how can the applicant be notified? He cannot see "private tickets". So we could also close it but then we should find another way to inform the applicant. Do you have any idea? silvio
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment -

              Yes... I also understand your point, I didn't realise he cannot view private tickets. But I'm not sure if there is a way to proceed in these cases. The only thing I know is that Manuel will call me if I have a ticket opened for more than 10 days

              Show
              aalonsog Alvaro Alonso added a comment - Yes... I also understand your point, I didn't realise he cannot view private tickets. But I'm not sure if there is a way to proceed in these cases. The only thing I know is that Manuel will call me if I have a ticket opened for more than 10 days
              Hide
              Permalink
              mev Manuel Escriche added a comment - - edited

              Yes, well, given the bug has been scheduled. You can inform now when it will be released.

              Show
              mev Manuel Escriche added a comment - - edited Yes, well, given the bug has been scheduled. You can inform now when it will be released.
              Hide
              Permalink
              silviocretti Silvio Cretti added a comment - - edited

              Yes I understand and agree.
              Let's do that:

              • close the ticket specifying the planned date for the correction of the bug
              • I will inform the applicant that the bug has been taken into consideration and about the delivery date
              • then I will keep open the ticket on HELC (corresponding to this ticket - HELC-1243)
              • then please inform me when the "private" ticket will be closed so I can inform the applicant and close the HELC ticket
                Thanks for this Alvaro
                silvio
              Show
              silviocretti Silvio Cretti added a comment - - edited Yes I understand and agree. Let's do that: close the ticket specifying the planned date for the correction of the bug I will inform the applicant that the bug has been taken into consideration and about the delivery date then I will keep open the ticket on HELC (corresponding to this ticket - HELC-1243 ) then please inform me when the "private" ticket will be closed so I can inform the applicant and close the HELC ticket Thanks for this Alvaro silvio
              Hide
              Permalink
              aalonsog Alvaro Alonso added a comment - - edited

              Thank you Silvio, I will do as you suggest. I've also added you as watcher of the private issue.

              BR

              Show
              aalonsog Alvaro Alonso added a comment - - edited Thank you Silvio, I will do as you suggest. I've also added you as watcher of the private issue. BR

                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: