Situation:
* Odoo v12.0 CE with multicompany database.
* Webserver (Apache2 reverse proxy).
Odoo database hosts backend functionality as well as publicly accessible website(s).
Questions:
Does it make sense to implement an authentication scheme at the webserver to increase security if Odoo server also hosts publicly accessible website(s)?
For example by using authentication forwarding (https://github.com/OCA/server-auth/tree/12.0/auth_from_http_remote_user).
In case of a publicly accessible website, Odoo server has many URL endpoints that need to be served without authentication.
What are website related end-points? We see many starting with "/web" which is also start of backend related URLs.
Can we discriminate between backend and website related URLs (e.g with <Location> configuration section containers in Apache conf) or is this not feasible / a bad idea?
Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
- CRM
- e-Commerce
- Buchhaltung
- Lager
- PoS
- Project
- MRP
Diese Frage wurde gekennzeichnet
2345
Ansichten
Diskutieren Sie gerne? Treten Sie bei, statt nur zu lesen!
Erstellen Sie heute ein Konto, um exklusive Funktionen zu nutzen und mit unserer tollen Community zu interagieren!
RegistrierenVerknüpfte Beiträge | Antworten | Ansichten | Aktivität | |
---|---|---|---|---|
|
0
Juni 25
|
314 | ||
|
0
Jan. 25
|
1418 | ||
|
0
Jan. 25
|
1459 | ||
|
1
Dez. 24
|
1927 | ||
|
0
Mai 24
|
1515 |