-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Technical] Upgrade Services to Spring #132
Comments
Ready for tech review by Meeds DAO members ( eXo: @rdenarie ) |
About the security part, and the Basic Authentication, is it possible to make it "activable" ? In some context, we need this authentication, but in other, for security reason, we need to close this door, and not expose endpoint with basic auth, because for example, we use a sso context like SAML or other, and we dont want that user access to rest endpoint with 'internal' exo account. So for me, some features are needed :
I speak about this point because you mentionned it in the security part, BUT, we have to discuss if this concern is part of this mip or not. |
The idea is to keep the same features as now without changes. Thus to not combine multiple concerns in one, which may lead to an excessive cost to this first outcome, both suggestions can be considered apart (same as API tokens which I suggested multiple times before, but not prioritized yet. Besides we will need this for Gamification Module interoperability) |
Ok, no problem. I came to this reflexion when viewing the security part, and after writing requirements, I remark that it was not the center of the MIP, so no pb to consider it in another MIP. |
Thanks for the feedback, Go-func added as well since no functional changes required on this. |
This change will upgrade services to use spring instead of Kernel & WS.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
Prior to this change, Portal database changelogs are processed late in the startup using PortalCotnainer. This change makes sure to initialize the database using RootContainer to make sure that the Database initialization is made before any other service startup.
Prior to this change, Portal database changelogs are processed late in the startup using PortalCotnainer. This change makes sure to initialize the database using RootContainer to make sure that the Database initialization is made before any other service startup.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
This change will upgrade services to use spring instead of Kernel & WS.
Merged to develop for |
…-io/MIPs#132 (#194) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
This proceed to migrate all Kudos API to use Spring DI instead of Kernel.
…-io/MIPs#132 (#328) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 (#522) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
This change will upgrade services to use spring instead of Kernel & WS.
…-io/MIPs#132 (#394) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 (#132) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
…-io/MIPs#132 (#1619) Prior to this change, App Center Data was injected at startup time using XML file. This change will introduce AppCenter applications using JSON format.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
This change will upgrade services to use spring instead of Kernel & WS.
Rationale
After Spring Integration MIP #57, the Service layer isn't completely which makes the usage isn't exclusively made by new technologies in new development. We will need the act the effective upgrade to Spring in Service layer in order to enforce the new development Best practice.
1. Functional Requirements
No functional changes has to be made.
2. Technical Requirements
Expected Volume & Performance
N/A
Security
Allow to access Spring REST using Basic authentication.
Extensibility
All Meeds REST endpoints has to be accessible using associated Web Archive of each extension.
Configurability
N/A
Upgradability
N/A
Existing Features
N/A
Feature Flags
N/A
4. Software Architecture
Security
Allow to access Spring REST using Basic authentication.
Access
All Meeds REST endpoints has to be accessible using associated Web Archive of each extension.
Services & processing
N/A
Data and persistence
N/A
The text was updated successfully, but these errors were encountered: