Page Comparison

...

1. Action items:
   1. High priority to test and verify if the current portal is working and plan to release the El Alto early drop - Lorraine A. Welch 
      • Issue with db connection authentication - Working with Sunder Tattavarada
   2. Dominik Mizyn  to add his comments/suggestions on 

      Jira Legacy
      server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key PORTAL-516

       - Springboot upgrade review.
      1. Hibernate upgrade - Started on DB layer - got into issues on mocked tests - need to adapt to latest java. (few more weeks to finish this)
         • blockers - some tables do not seemed to be mapped in hibernate (Dominik will send details in email)
      2. Java and springboot upgrade (in next release - for El Alto)
         • blockers - do not know how to correctly configure Maven to work with two Java versions - https://vladmihalcea.com/maven-and-java-multi-version-modules/
         • hard to identify the services that use the backend objects as the names are not matching - for example: PersUserWidgetService, ENPersWidgetSel uses different objects.
      3. New folder proposal move from older folders "ecomp-portal-*" to new folder "portal-*".
      4. Propose themeleaf usage and its benefits - Dominik
      5. Dominik to schedule as session to setup local workspace for unit testing before submitting the code changes.
   3. Analyze Java upgrade to latest version along with springboot upgrade - Need to create a user story.
   4. Followup with Jessica on JJB migration - Lorraine
   5. Design documentation on OJSI - 190 - Sunder Tattavarada
   6. Saisree to provide update versions for few components - Sunder Tattavarada/Saisree - Notified to Pawel
   7. PORTAL-668 - Create a Jira item to notify the breaking changes on portal due to portal/sdk changes. (submodule changes and merge jenkins jobs changes) - Lorraine A. Welch
2. Database DML and DDL scripts, including Apps_Users_Onboarding_Script.sql and oom_updates.sql. (target for El Alto final release)
   1. Naming conventions currently 
   2. Are migration scripts necessary or just fresh installs? (from Dublin to El Alto release)
      1. MariaDB - https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_user_guide.html#upgrade
      2. Cassandra - only fresh installs are necessary
   3. Proposed from last week: Move  Apps_Users_Onboarding_Script.sql from Portal/Deliveries  to OOM directory ([oom.git] / kubernetes / portal / charts / portal-mariadb / resources / config / mariadb / )
   4. Proposed from last week: Sunder will disable the old  Apps_Users_Onboarding_Script.sql in the old image
3. OJSI - 190  user/passwords in Portal?
   1. AAF supports passwords for users. ask Jonathan for user/password authentication
   2. does CADI have session cookie? fallback -  hash the passwords. 
   3. App id/password for system to system - their password needs to be hashed too
   4. AAF now stores password hashed ; supports basic AUTH (is not hashed, just encoded)
   5. Portal partners don't have to hash their own but Portal needs to hash them
   6. should be reasonable to plugin CADI - do they support cookie-based?
   7. Changes will be for  user to system and system to system

...