You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update properties
* Upgrade GHA to use Node.js 20
* Improve handling attributes in firewall
* Modify SecurityConfig to use CORS config from property file
* Fix wss ssl
* Update pom.xml to use latest MMP
* Update CHANGELOG.md and README.md
* Address PR comments
* Update test to check PUT method, since OPTIONS is now allowed in
Firewall
Copy file name to clipboardExpand all lines: README.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,35 @@ allowUrlEncodedPeriod=true
97
97
```
98
98
*IMPORTANT:* If you're not an expert, the strong advice is to keep values at their default values. If you decide to change values, pay special attention to allowHeaderNames and allowHeaderValues, since those set values are exclusive and considered as only values that should be present in the header.
99
99
100
+
## CORS Configuration
101
+
102
+
In order to communicate with UI, CORS (Cross-Origin Resource Sharing) settings should be configured in `application.properties` file. This allows you to specify which origins, methods, and headers are permitted when making cross-origin requests to your application.
103
+
104
+
```
105
+
application.cors.allowed.origins=
106
+
application.cors.allowed.methods=
107
+
application.cors.allowed.headers=
108
+
```
109
+
110
+
-`application.cors.allowed.origins`: Specifies the allowed origins. If empty, all origins (*) are allowed.
111
+
-`application.cors.allowed.methods`: Specifies the allowed HTTP methods. If empty, all methods (*) are allowed.
112
+
-`application.cors.allowed.header`s: Specifies the allowed headers. If empty, all headers (*) are allowed.
0 commit comments