Bindaas Admin Guide

In this page, we discuss the common administration tasks related to Bindaas in detail.

How to disable Bindaas authentication?

If you like to turn off the use of api keys to consume the Bindaas services, you can easily turn them off from the bin/bindaas.config.json as below:

"enableAuthentication": false,

With the authentication enabled, a valid query for a service will be as below:

curl http://localhost:9099/services/test/mongo/query/find?api_key=d9076d81-147d-44c3-9af6-d3dc5d9f204wb

A query such as the below without the api_key will fail when the authentication is enabled, whereas it will succeed when the authentication is disabled.

curl http://localhost:9099/services/test/mongo/query/find

Can I use X instead of Bindaas' own authentication capabilities?

Definitely! You can disable the authentication provided by Bindaas in favor of using an authentication provider external to Bindaas. For example, you may configure Bindaas with Kong as the authentication provider.

How to change the admin dashboard port from 8080 to something else?

You have two options.

i) Pass the new port as an argument:

java -Dorg.osgi.service.http.port=8082 -Djava.net.preferIPv4Stack=true -Dpid=BINDAAS_INSTANCE -Xmx1024m -jar org.eclipse.osgi_3.8.2.v20130124-134944.jar -console

ii) Change the below line in bin/configuration/config.ini from 8080 to something else:

org.osgi.service.http.port=8081

If both (i) and (ii) are configured, the input in the console argument takes precedence. i.e., the dashboard uses the port 8082 above.