CODEWITHSUNDEEP
orientdborientdb-2.1
tarka
tarka

Reputation: 5587

OrientDB Could not access the security JSON file

Following my upgrade from OrientDB 2.1.16 to 2.2.0 I have started to get the following messages during the initialisation:

2016-05-19 09:28:38:690 SEVER ODefaultServerSecurity.loadConfig() Could not access the security JSON file: /config/security.json [ODefaultServerSecurity]
2016-05-19 09:28:39:142 SEVER ODefaultServerSecurity.onAfterActivate() Configuration document is empty [ODefaultServerSecurity]

The database launched but I don't like the warnings. I've looked through the docs but I cant find anything specifically pertaining to this. There are some links on Google that lead to dead Github pages.

Upvotes: 1

Views: 556

Answers (1)

Colin
Colin

Reputation: 121

There are 3 ways to specify the location and name of the security.json file used by the new OrientDB security module.

1) Specify the environment variable, ORIENTDB_HOME, and it will look for it here: "${ORIENTDB_HOME}/config/security.json"

2) Set this property in the orientdb-server-config.xml file: "server.security.file"

3) Pass the location by setting the global variable -Dserver.security.file on startup.

Here's the documentation on the new features + a link to the configuration format.

https://github.com/orientechnologies/orientdb-docs/blob/master/Security-OrientDB-New-Security-Features.md

-Colin OrientDB LTD The Company behind OrientDB

Upvotes: 4

Related Questions