gokintosh / user-service

User-service

Roles:

ROLE_USER : Normal User, who signed up for the app.

• Has the ability to view their profile, edit.

• View trash coins earned.
• View leader board.
• and much more.

ROLE_ADMIN : User who are allowed to access specific route by the moderator. Normally people from the urzad.

• has the ability to view their profile, user profile, edit or deactivate certain user.

• Admin dashboard from the front end. !!Todo🤔

ROLE_MODERATOR : People who work on the app (creator of the app).

• has the ability to view their profile, admin profile and userProfile.
• super-user Capability.

Test the service locally 📍

Clone the Repo

1. use git clone command to clone the repo.
   
2. After cloning install all maven dependency.
   
3. setup database of your choice and add respective dependency for maven. configure main/java/resources/application.properties.
4. Run the service using the ^R (mac).
5. Application starts without any errors.

Test API endpoints using POSTMAN📮
create user
POST http://localhost:8080/user/auth/register

{
    "username":"Marcin",
    "email":"[e-mail]",
    "role":[
        "user","admin","mod"
    ],
    "password":"marcinkaminski"
}

here we take basic inputs from the frontend along with roles. and store this data in backend.

todo : response status for now is just a string we will implement email verification to activate account later on.

login user
POST http://localhost:8080/user/auth/signin

{
    "username":"Marcin",
    "password":"marcinkaminski"
}

we login user with username and password. This creates stateless authentication for user.

we will return a JWT token like this one:

eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJNYXJjaW4iLCJpYXQiOjE2NjcxMzQ4MjksImV4cCI6MTY2NzIyMTIyOX0.DE2x_r4Ddx19JURDK1QGvUAi3150TSewZCWzsJP07d2eTHoBeHp6ggKkV0a1Ra-ovLO5Ndy8t4_IfmIYizlTXg

what values does this token contains?

we store this token inside browser and each tie when we send a request, we user this token as Authorization header as a bearer token.

Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJNYXJjaW4iLCJpYXQiOjE2NjcxMzQ4MjksImV4cCI6MTY2NzIyMTIyOX0.DE2x_r4Ddx19JURDK1QGvUAi3150TSewZCWzsJP07d2eTHoBeHp6ggKkV0a1Ra-ovLO5Ndy8t4_IfmIYizlTXg

So when the request reaches the endpoint at spring backend, the custom filters, will validate the token and extracts details on authority and username.

Some routes require authorization. So depending on the ROLE specified, the user get redirected to resource or not accessible page.

Example (tried with a user who does not have access to non admin route)

more to come....

created by
gokintosh🤖