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

FIWARE.Request.Lab.Re: Regarding new Cloud and Security GEs releases.

    Details

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

      Description

      Dear FIWARE Lab team,

      we are not sure if we have to take some action after your message regarding
      the upgrade of the Identity Manager.
      We are currently using the public instance of the identity manager with the
      cloud portal to offer a "Login with FIWARE" feature in a couple of our
      applications.
      Do we have to take some action in order to avoid problems with the
      authentication?

      Thank you,
      Leonardo Dal Zovo - Studiomapp srl

      2017-07-17 17:08 GMT+02:00 <no-reply@account.lab.fiware.org>:

      > [image: FIWARE-Lab]
      >
      > Dear FIWARE Lab user,
      >
      > as we announced few days ago, we are going to upgrade the current Cloud
      > and Security GEs instances deployed in FIWARE Lab. As a result of the new
      > release of Cloud Portal, and trying to improve its usability, the way in
      > which you access to this portal has changed. This upgrade also affects the
      > way in which Wilma PEP Proxy GE validates OAuth2 tokens with the FIWARE
      > Identity Management.
      >
      > IMPORTANT: the following instructions only apply to users of Cloud Portal
      > and Wilma GEs. If you are not using these components you can safely ignore
      > the rest of the message.
      >
      > - Cloud Portal GE:
      >
      > From tomorrow's upgrade, Cloud Portal users will have a specific account
      > to login in this portal. Of course, you could continue logining using the
      > same username (email) and password that you are currently using. But if you
      > do changes in this account (e.g. changing the password) these changes will
      > only apply to the Cloud Portal account and not to the FIWARE Lab Account
      > Portal one.
      >
      > On the other hand, we are going to change the web interface of the Cloud
      > Portal, using a Openstack Horizon based interface. We hope this improves
      > the usability of this portal.
      >
      >
      > - PEP Proxy GE:
      >
      > With the new deployment, PEP Proxies will have to validate tokens with
      > Identity Manager server. You will have just to change the validation
      > address in your PEP Proxy’s configuration file. In the parameter
      > “config.keystone_host” you will have to set the address “
      > account.lab.fiware.org”.
      >
      >
      > If you have any doubts regarding these changes, you can contact FIWARE Lab
      > team as always in fiware-lab-help@lists.fiware.org.
      >
      > Best regards,
      >
      > FIWARE Lab team.
      >
      >
      > —
      > You are receiving this message because you are a registered FIWARE Lab
      > user <https://account.lab.fiware.org>. Should you wish to remove your
      > account, you need to follow four simple steps:
      >
      > 1. Log on FIWARE Lab user <https://account.lab.fiware.org>
      > 2. Click on the dropdown menu next to your user name (upper right
      > corner)
      > 3. Select "Settings"
      > 4. Click on "Cancel account" and confirm.
      >
      > 2015 © FIWARE <http://www.fiware.org/>.
      >

      __________________________________________________________________________________________

      You can get more information about our cookies and privacy policies on the following links:

      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: Studio Mapp <studiomappit@gmail.com>]

        Activity

        Hide
        fla Fernando Lopez added a comment -

        Dear Leonardo,

        During the migration to the new Security component, Keyrock must be down, which means that no token validation or access to the Cloud. We made yesterday a first intent to make this migration but we detect a problem and we made a backward activity. Today we analyse the problem detected and we will try again during this week.

        Our intention is not doing it for the next week, taking into account the review of the SmartSDK.

        Best regards,

        Fernando

        Show
        fla Fernando Lopez added a comment - Dear Leonardo, During the migration to the new Security component, Keyrock must be down, which means that no token validation or access to the Cloud. We made yesterday a first intent to make this migration but we detect a problem and we made a backward activity. Today we analyse the problem detected and we will try again during this week. Our intention is not doing it for the next week, taking into account the review of the SmartSDK. Best regards, Fernando

          People

          • Assignee:
            fla Fernando Lopez
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: