This section will cover information about Gentics Mesh security related topics.
API tokens can be generated via the
These tokens should not be publicly exposed since they they are equivant to user credentials.
Tokens can be reset via the
This will invalidate any previously generated API token.
Gentics Mesh can provide various internal services which each utilize dedicated ports. By default only the REST and GraphQL API on port 8080 will be exposed. The REST and GraphQL API is secured by the Gentics Mesh authentication mechanism.
|Exposing this service would allow anyone to modify, read and delete any of the data within the search index. User passwords are not stored within this index.|
Search queries can be submitted via the
The storage.startServer setting can be used to start the OrientDB server on port 2424 and 2480. This server will automatically be started if the cluster.enabled setting is enabled. It is advised to not expose this service.
The cluster.enabled setting will startup the OrientDB server as described above. Additionally the Vert.x eventbus, ElasticSearch clustering and Hazelcast service will be started. All these services will open dedicated ports which will bind to the network which can be configured via the cluster.networkHost setting.
|Do not expose the service ports which are listed in the clustering documentation to the internet.|
The Elasticsearch server will automatically open port 9200. Keep in mind that this service should never be exposed publicly since it is not protected by any authentication mechanism.
User passwords are stored as bcrypt hashes.
Please do not post security issues to our github issues page. Instead we encourage you to submit security issues to us via email@example.com
Publicly disclosing a vulnerability can put the entire community which makes use of Gentics Mesh at risk.
Your disclosure should include:
A description of the issues
A list of steps which can be followed to reproduce the issue