Thomas Jaeckle
Thomas Jaeckle
Ditto shall support configuring that per namespace a declared set of policy IDs are always imported, acting as kind of "namespace/tenant root policy". It is sufficient to configure that statically,...
Define that a policy entry is only applicable for entities within a certain or several certain namespaces. This feature is especially useful when used in combination with policy imports and...
**Currently**, Ditto provides a very advanced (e.g. supporting partial requests/updates, "PATCH" updates, server sent events for notifications) HTTP API to be **consumed by either frontends, mobile applications or even backends**....
The idea of this issue is to have a special kind of JSON values inside a Ditto Thing (e.g. as `attribute` or as `feature` `property`) which are not directly available...
Utilising the MongoDB search index, Ditto could support aggregation queries via its search API, e.g. in order to find out the mean temperature value of hundreds/thousands of selected things. Our...
For Ditto managed connections, configuring a payload mapper is possible, either using one of the built in ones, using the Javascript mapper providing a script file or even adding one...
Some HTTP APIs might e.g. support "Bearer" authentication, but provide a non-OAuth or non-OpenIdConnect endpoint for obtaining JWT. E.g. a custom "POST /authenticate" endpoint which delivers a JWT. In order...
Initial draft of CoAP support in Ditto gateway: * provides (currently unsecure, plain UDP) CoAP endpoint * providing equivalent CoAP resources as the HTTP resources: * /things, /policies, /whoami *...
I am trying to get vagrant-proxyconf running with Ubuntu Snappy 15.04: `config.vm.box = "http://cloud-images.ubuntu.com/snappy/15.04/core/stable/current/core-stable-amd64-vagrant.box"` Config is: ``` if Vagrant.has_plugin?( "vagrant-proxyconf" ) config.proxy.http = "my.proxy.de:3128" config.proxy.https = "my.proxyde:3128" config.proxy.no_proxy = "localhost,127.0.0.1"...
E.g. in order to put something on the session in a "feeder" loop and access it when using `amqp("..").publish()`: ``` val scn = scenario("Create via AMQP") .exec( amqp("Consume response").consume("response_queue", autoAck...