- May 06, 2023
-
-
-
-
Juraj Paluba authored
-
Juraj Paluba authored
-
Juraj Paluba authored
-
Juraj Paluba authored
To build service images use either `docker compose build` or in the service folder `docker build -t <my-name> -f Dockerfile ../`
-
- May 05, 2023
-
-
Juraj Paluba authored
-
Juraj Paluba authored
Create a new secure profile which configures authorization servers (github and MUNI) as well as secures API endpoints. By default the application is started in insecure mode. Meaning that no login is required (good for scenario) and all API endpoints do not require any authentication whatsoever. To secure the application you must activate the 'secure' profile. For example run the following: `mvn spring-boot:run -Dspring-boot.profiles=secure` or when running as jar: `java -Dspring.profiles.active=secure -jar my-epic-jar-file.jar`
-
Juraj Paluba authored
And generalized AuthUserService classes. Updated tests. Only those that needed admin persmissions.
-
Juraj Paluba authored
-
Juraj Paluba authored
Created new application property that takes list of emails. If user is logged in using any of these emails, it will assing admin privileges to him.
-
Juraj Paluba authored
Had to allow actuator endpoint in core service. The application properties were using deprecated key for enabling. No need to specify special version for org.springframework.org dependencies as they are defined in parent pom.
-
Daniel Timko authored
-
Daniel Timko authored
-
Daniel Timko authored
-
Daniel Timko authored
-
Daniel Timko authored
-
- May 04, 2023
-
-
- May 03, 2023
-
-
Had to add spring security test dependency as well as WithMockUser annotation (for rest controllers --> performing requests with given user) and MockedBeand for client registration. It is not the optimal solution, but honestly the only one I was able to produce. The main problem is the securityFilterChain in App class besides main(). Because the App class is executed during each test.
-
Login providers are Github and MUNI. To login just go to http://localhost:8080 and choose preffered login provider. New services are used to create our User entity in database. The intended use case is that every time we will need user, we can find him by his email. Of course the authentication is not setup properly as it does not differantiate between admin and normal user. That will come in second iteration.
-
-
-
-
Notice that compared to the seminars, I am not using the ":" in applicaiton.properties. For some reason, in our version of spring it is not supported. If used, it will be ignored, but there would be no warning or error. To log in, simply go to http://localhost:8080 and login using your github credentials, authorize the service to use your information (specified in scopes) and you will be redirected to Demo page.
-
The web page will be used as redirect after successful login.
-
- May 02, 2023
-
-
- May 01, 2023
-
-
Juraj Paluba authored
With profile specified in build configuration, the spring-boot:run would always use the production application properties. Thus, it will try to create connection with postgres DB in container.
-
- Apr 28, 2023
-
-
- Apr 26, 2023
-
-
xmihale authored
Eager fetch type fix, rest mapping persons -> people, resolving stack overflow exception when entities used hashCode
-
- Apr 19, 2023