Skip to content

Commit d378ace

Browse files
authored
Update README.md
describe my project
1 parent 10774c3 commit d378ace

File tree

1 file changed

+15
-1
lines changed

1 file changed

+15
-1
lines changed

README.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,15 @@
1-
# spring-oauth2-minio-api
1+
# spring-oauth2-minio-api
2+
## Teck Stack:
3+
Spring boot , oauth2 , liquibase , Minio-api for file management , Postgres DB and Pgadmin using docker compose file
4+
5+
1) The flow of the project is the normal oauth2 flow where i am using Password grant_type
6+
2) I am using refreshing mechanism and as we all know the refreshing mechanism is responsibilty of client so my client in my case was Postman
7+
so, within the collection in the repo you will find [ pre-request ] script to check whether the access_token expired or not
8+
i mean you didn't need to call the request for token api just call the resource server's endpoint directly and it will work as inside the authorization header I passed the collection variable that i set the token insdie when the token expired
9+
10+
3) i defined liquibase script to define 2-admin users [Rohan , Bushra] so i can use them to request token from the server
11+
12+
4) the resource server deal with file management so, i used Minio's Api where Minio allows the upload and download of files for containerized applications, respecting the interfaces of Amazon S3 solution using the terms of amazon S3 like bucket but upload your files to your own server not on the cloud
13+
but in my case instead of put extra configuration as it is just task i used the public server of minio company which is https://play.min.io/minio/
14+
15+
5) I added Unit Test and Integration Test to my code using Junit 5 (jupiter) and mockito

0 commit comments

Comments
 (0)