On Fri, Oct 19, 2018 at 6:04 AM Hudalla Kai (INST/ECS4) <
kai.huda...@bosch-si.com> wrote:
> On Thu, 2018-10-18 at 21:56 +0100, Gordon Sim wrote:
> > On 18/10/18 15:07, Hudalla Kai (INST/ECS4) wrote:
> > > I am supplying them from the auth service in the same format that
> worked in
> > > 1.1.0.
>
On Thu, 2018-10-18 at 21:56 +0100, Gordon Sim wrote:
> On 18/10/18 15:07, Hudalla Kai (INST/ECS4) wrote:
> > I am supplying them from the auth service in the same format that worked in
> > 1.1.0.
>
> This is not a result of any change in the auth plugin itself. Since
> 1.2.0, setting the valid so
On 18/10/18 21:56, Gordon Sim wrote:
The fix is straightforward. I'll update the tests to ensure we don't
regress on this aspect again.
https://issues.apache.org/jira/browse/DISPATCH-1149, fixed on master
-
To unsubscribe, e-m
On 18/10/18 15:07, Hudalla Kai (INST/ECS4) wrote:
I am supplying them from the auth service in the same format that worked in
1.1.0.
This is not a result of any change in the auth plugin itself. Since
1.2.0, setting the valid sources and targets on the policy_settings of
the connection no lon
On Thu, 2018-10-18 at 14:43 +0100, Gordon Sim wrote:
> On 18/10/18 10:04, Hudalla Kai (INST/ECS4) wrote:
> > here is the router configuration file I am using:
> >
> > [
> >["router", {
> > "id": "Hono.Example.Router",
> > "mode": "standalone",
> > "workerThreads": 3
> >}],
>
On 18/10/18 10:04, Hudalla Kai (INST/ECS4) wrote:
here is the router configuration file I am using:
[
["router", {
"id": "Hono.Example.Router",
"mode": "standalone",
"workerThreads": 3
}],
["authServicePlugin", {
"name": "Hono Auth",
"host": "10.56.84.13",
Hi,
I have been successfully using the (experimental) SASL auth plugin feature with
Dispatch Router 1.1.0. I had implemented an auth service and configured the
router to use it for authenticating clients and authorizing requests to
establish
links.
I have now tried to use the same auth server wi
