AC 1: Add Spring security
AC 2: Implement Basic Auth

AC 1: content type - application/json
AC 2: returns all available journeys
AC 3: Support pagination
AC 4: Support sorting

Basic support for query param:

• "sort" - sorting column name
• "order" - ASC or DESC
• "pageIndex" - starts from 0
• "pageSize" - maximum number of journeys to return in response

New field 'visibilities' added to journey.
Implement authorisation based on the field as follows,

AC 1: If LoggedIn user is ADMIN, then all journeys
AC 2: If LoggedIn user is GUEST, then only journeys which contains GUEST role
AC 3: If LoggedIn user is USER, then all journeys contains any(GUEST, AUTHENTICATED_USER) and and journeys created by themself if any
AC 4: If LoggedIn user is MAINTAINER, then all journeys contains any(GUEST, AUTHENTICATED_USER, MAINTAINER) and journeys created by themself

AC 1: ADMIN rolled user can see all journey
AC 2: MAINTAINER rolled user can see their owned journey and system default journeys
AC 3: GUEST rolled user can see only system default journeys

Get the coordinates of a place

1. On your computer, open Google Maps.
2. Right-click the place or area on the map.
3. This will open a pop-up window. You can find your latitude and longitude in decimal format at the top.
4. To copy the coordinates automatically, left click on the latitude and longitude.

Tips:

1. List your latitude coordinates before longitude coordinates.
2. Check that the first number in your latitude coordinate is between -90 and 90.
3. Check that the first number in your longitude coordinate is between -180 and 180.

ailed to bind properties under 'jwt.public-key' to java.security.interfaces.RSAPublicKey:
Property: jwt.public-key
Value: "/etc/secrets/jwt-public.pub"
Origin: class path resource [application.yml] from journey-api.jar - 19:15
Reason: failed to convert java.lang.String to @jakarta.validation.constraints.NotNull java.security.interfaces.RSAPublicKey (caused by java.io.FileNotFoundException: class path resource [etc/secrets/jwt-public.pub] cannot be opened because it does not exist)

At the moment, only http status 201 being send to client when new journey created.
It will be helpful if we can send created journey entity id along with other details in response to create journey request.

AC 1: Only ADMIN rolled user can create user
AC 2: Define "GUEST" user details and with "GUEST"
AC 3: follow user details service prototype implement necessary details

1. When delivering geo json data, we can use standard content type "application/geo+json" and similarly for accept header while requesting

1. Add Spring bot actuator
2. Find appropriate health endpoint for application availablity
3. Configure the endpoint on Render for zero down time

Nice to support,

• 1. text
• 2. city
• 3. country
• 4. category
• 5. journeyYear
• 6. isPublished
• 7. tags
• [ ]

https://www.baeldung.com/spring-security-authentication-with-a-database
https://docs.spring.io/spring-security/reference/servlet/authentication/passwords/user-details-service.html

AC 1: Implement update feature http method PATCH
AC 2: Reusable to update partial data
AC 3: Define data types can be updated independently
AC 4: validation implemented
Ac 5: stored in DB

1. Add new "name" field to user
2. Return the name in login response

compare all authority variant.
e.g. to compare GUEST_USER authority, include ROLE_GUEST_USER, SCOPE_GUEST_USER and GUEST_USER for comparison.

AC 1: auth login flow /auth/login

Add below visibilities as default visibility while creating journey,

1. MYSELF
2. ADMINSTRATOR

Allow OPTIONS preflight requests for SPA.

If we could add createdDate and journeyDate, it would be really helpful for frontend sorting.

1. Define data model for core Journey object
2. Define suitable geometric class for location
3. find below minimum data fields required for now.

"id": "id_1", "type": "Feature", "geometry": {"type": "Point", "coordinates": [11.6634, 48.1230]}, "properties": { "name": "München House", "category": "Residential", "city": "Munich", "country": "Germany", "tags": ["Ram", "Sakunthala", "Germany", "Munich"], "description": "Remember that happiness is a way of travel, not a destination.", "thumbnail": "/assets/test-data/img/2022_1.png"

AC 1: implement new field "visibility" for journey
AC 2: the new field editable while publishing journey
AC 3: the new field can have value as follows,

1. Myself (by default checked and disabled)
2. Administrator (by default checked and disabled)
3. Maintainer
4. Authenticated User
5. Guest

AC 4: Update journey authorization mechanism based on the new visibility field

1. Deploy webhook url has confidential key. so keep it secured.
2. Update GitHub action to trigger the webhook after successful build for tag

AC 1: Implement rest endpoint to get journey data with id
AC 2: in json format if accept type application/json
AC 3: throw error if id not exists
AC 4: connect to db and fetch data

https://github.com/spring-projects/spring-security-samples/tree/main/servlet/spring-boot/java/jwt/login

1. define Journey entity based on json attached
2. Define REST endpoint to store journey with Request and response DTO
3. Define entity
4. Store the entity in Database

AC 1: endpoint PUT /journey/{id}
AC 2: Content Type "application/vnd.journey.api.images.v1+json"
AC 3: Payload

{
"url": <string>,
 "assetId": <string>
}

Analyse and implement 2FA features,

1. Email Code Verification
2. TOTP
3. If possible push notification with GitHub, Microsoft Authenticator

when PublishedOnly is true, should provide journeys which all are published.
Whereas when PublishedOnly is false, should provide both published and unpublished journeys.

Class cast exception while assigning authenticated principal to user details.