Skip to content
Extraits de code Groupes Projets
Pour retrouver l'état du dépôt de ce projet au moment de chacune de ses versions, extrayez-en les étiquettes.

[1.0.4]

Added

  • adding dtos : ElementContentDTO and InnerFileDTO
  • Adding feature of : getting files within a certain tender analysis folder

Changed

  • Docs controller : exposing the detailed content feature via endpoint
  • Docs service : by defining a detailed folder content getter function : getDetailedFolderContent
  • updating the docs service (features of defining a new analysis folder) and adapting the controller.
  • MP-339: Updated getUserRoles(Long userId) to return the role assignment date from database

[1.0.3]

-MP-350 : Apply filtering and pagination on the backend side rather than the frontend.

  • MP-330: Add filtering to the GET /roles endpoint.
  • MP-330: GET /roles endpoint now returns roles sorted from newest to oldest.

[1.0.2]

Added

  • Adding features of : defining a certain analysis folder + importing files withing this latter
  • Adding File repository + Docs Controller & Service
  • MP-333: added the endpoint DELETE /roles/{id} for deleting a role by its ID (can only be consumed by users that have the permission DELETE (ROLE_MANAGEMENT)).
  • MP-174: add the endpoint /users/me to get the profile of the current user.
  • MP-180 : add the endpoint Put /logout to close a connection session.
  • MP-179 : Add the endpoint Get /connection-history to retrieve the histories of a connection.

Changed

MP-334: modified the endpoint PUT /roles/{id}/status?isActive={boolean} so now only users with the permission UPDATE_STATUS can consume it. MP-330 : changed endpoint GET /roles so that now the page number and page size can be configured for pagination (ex: /roles?page=1&size=5). MP-372 : changing paths constant and test MP-328 : Modified getUserById and getAllUsers methods to return the updated UserWithStatusDTO.

[1.0.1]

Added

MP-372 : adding service to get id by mail

[1.0.0]

Added

  • Added functionality for role creation alongside permissions setting and users

  • Adding feature : Admin confirms user creation

  • Adding feature : admin logs in

  • Adding feature : Admin confirms user creation

  • Adding feature : set new password after recovery demand

  • Adding features : demand password + check recovery.

  • Adding feature of updating a user password by an admin.

  • Setting up authentication features territory, adding first 2 features : authenticating user + creating user

  • Initial configuration of the mobimarche-user-management-service application

  • Created application.yml and application-local.yml for environment-specific settings

  • Set server port to 6061

  • Configured PostgreSQL database connection for the local environment

  • Enabled Hibernate automatic schema update (ddl-auto: update)

  • Enabled SQL query logging (show-sql: true)

  • Set up @ComponentScan for com.marketingconfort.starter.core and com.marketingconfort.mobimarche.*

  • Configured @EnableJpaRepositories for starter and user management repositories

  • Defined @EntityScan for starter and user model packages

  • Add the mappers PermissionRequest and PermissionResponse.

  • Add the PermissionService and its implementation PermissionServiceImpl along with the necessary paths.

  • Add the PermissionController.

  • Add the PermissionInitializer to initialize default permissions during application startup.

  • Add the SecurityConfiguration class to configure global security settings, allowing all requests and disabling CSRF protection.

  • Add GET /permissions/{id} endpoint to PermissionController to retrieve a permission by its ID.

  • Add Get /Permissions endpoint to PermissionController to retrieve all permissions.

  • Add Post /users endpoint to create User and service layer implementation

  • Add createRole method to the controller

  • Create POST /roles endpoint in RoleController to add new roles

  • Add GET /users endpoint to retrieve all registered users

  • Create GET /roles endpoint in RoleController to retrieve all roles

  • Create a GET /roles/{id} endpoint in the RoleController to retrieve a role by its ID

  • Create a DELETE /roles/{id} endpoint in RoleController to delete a role by its ID

  • Add GET /user-permissions endpoint to UserPermissionController to retrieve all permissions for a user

  • Implement GET /users/{id} endpoint to fetch user details

  • Add user status update functionality via PUT /users/{id}/status endpoint

  • Implement PUT /users/{id} endpoint to update user details

  • Create a PUT /roles/{id} endpoint in the RoleController to update role information by its ID

  • Add POST /user-permissions/assign endpoint to the UserPermissionController to assign permission(s) to a user

  • Create a PUT /roles/{id}/status endpoint in RoleController to updates the active status of a role by its ID

  • Assigns a list of permissions to a specified role

  • Create a PUT /roles/{id}/status endpoint in RoleController to updates the active status of a role by its ID

  • Create DELETE /roles/{roleId}/permissions Removes one or more permissions associated with a specific role

  • Implement GET /roles/{roleId}/permissions endpoint to get permissions by roleid

  • Implement GET /user-roles/{userId} endpoint to fetch all roles linked to a specific user.

  • Create POST /user-roles/assign endpoint to assign one role to a user

  • Add GET /user-roles/users-by-role/{roleId} endpoint to retrieve users assigned to a specific role with response mapped to UserResponseDTO

  • Add DELETE /user-roles/remove endpoint to allow the removal of a specific role from a user

  • Create PATCH /update-active-state endpoint to activate/deactivate a user role

  • Add DELETE /user-permissions/remove endpoint to the UserPermissionController to remove permission(s) from a user

  • Add the MessageConstants class to centralize and manage exception messages.

  • Add the PUT /user-permissions/update-status endpoint to update the status of one or more permissions for a user.

  • Implement GET /status-history endpoint to record and retrieve the history of status changes.

  • Implement the GET /permissions/grouped endpoint to group permissions by module name

  • Add DELETE /remove endpoint to remove multiple roles from a user

  • Implement user status change with history tracking

  • Add CorsConfig class to configure CORS settings and resolve multi-value Access-Control-Allow-Origin header error

  • Improve getAllRolesWithGroupedPermissions logic in RoleServiceImpl

  • CHANGED

  • Changing the mapper to cover the correct role while creating a certain user

  • Changing local config : setting up correct mailing config.

  • Updated UserMapper to include mapping of createdAt, photoUrl, and lastLogin fields to UserResponseDTO.

  • Added createdAt and lastLogin fields to UserResponseDTO.

  • These changes were made to fulfill frontend requirements for user listing.

  • Add the state attribute to the UserRequestDto and UserResponseDto.

  • Map state field in both UserMapper.toEntity and UserMapper.toResponseDTO.

  • Remove