DEBUG: mysite:34
{acl_mqtt,direct,<<"site/mysite/flight">>,[<<"site">>,<<"mysite">>,<<"flight">>],<<"mysite">>,<<"uRBtcIBLWCKpWoslTfiR">>}
I see it in the console, what does it mean?
четверг, 1 декабря 2016 г., 1:36:51 UTC+9 пользователь Marc Worrell написал:
>
> Just to be sure, it is a modu
modul called without mod_,does it matter?
четверг, 1 декабря 2016 г., 1:36:51 UTC+9 пользователь Marc Worrell написал:
>
> Just to be sure, it is a module as in “mod_something.erl” ?
> And other observers in that module are called?
>
> - Marc
>
>
>
> On 30 Nov 2016, at 17:30, heiheshang >
> wro
Yes
-export([observe_acl_is_allowed/2]).
and mod_prio(10)
but another module mod_prio(600) and all work
четверг, 1 декабря 2016 г., 1:18:32 UTC+9 пользователь Marc Worrell написал:
>
> The function is exported?
>
> Maybe make the priority of you module a bit higher.
> Set it to 10 or so.
>
> -mod_p
Just to be sure, it is a module as in “mod_something.erl” ?
And other observers in that module are called?
- Marc
> On 30 Nov 2016, at 17:30, heiheshang wrote:
>
> subscription works only in one module, other modules in the code is not
> running. The priority of the module is 10.
> in other
subscription works only in one module, other modules in the code is not
running. The priority of the module is 10.
in other modules? DEBUG does not work, do not understand why is not
called -export([observe_acl_is_allowed/2]).
четверг, 1 декабря 2016 г., 1:18:32 UTC+9 пользователь Marc Worrell н
The function is exported?
Maybe make the priority of you module a bit higher.
Set it to 10 or so.
-mod_prio(10).
- Marc
> On 30 Nov 2016, at 17:14, heiheshang wrote:
>
> observe_acl_is_allowed(X,Context) ->
> ?DEBUG(X);
>
>
> He added, but there is no output
>
> четверг, 1 дека
observe_acl_is_allowed(X,Context) ->
?DEBUG(X);
He added, but there is no output
четверг, 1 декабря 2016 г., 0:59:01 UTC+9 пользователь Marc Worrell написал:
>
>
> On 30 Nov 2016, at 16:52, heiheshang >
> wrote:
>
> observe_acl_is_allowed(#acl_is_allowed{action=publish,
> object=#ac
> On 30 Nov 2016, at 16:52, heiheshang wrote:
>
> observe_acl_is_allowed(#acl_is_allowed{action=publish,
> object=#acl_mqtt{words=[<<"~site">>,<<"flight">>| _Rest]}}, Context)
> ->
> true;
> observe_acl_is_allowed(#acl_is_allowed{action=subscribe,
> object=#acl_mqtt{words=[<
observe_acl_is_allowed(#acl_is_allowed{action=publish,
object=#acl_mqtt{words=[<<"~site">>,<<"flight">>| _Rest]}},
Context) ->
true;
observe_acl_is_allowed(#acl_is_allowed{action=subscribe,
object=#acl_mqtt{words=[<<"~site">>,<<"flight">>| _Rest]}},
Context) ->
true;
obser
> On 30 Nov 2016, at 16:10, heiheshang wrote:
>
> yet this only works for the administrator, all other users do not receive
> messages
Probably due to the <<“~site”>> in your pattern.
Administrators have a shortcut in all ACL checks, so that they can do anything
regardless of ACL modules.
So
yet this only works for the administrator, all other users do not receive
messages
среда, 30 ноября 2016 г., 23:37:13 UTC+9 пользователь Marc Worrell написал:
>
> Check the “words” that pass here, shorthands like “~site” will already be
> expanded here.
>
> In your case you can match on: [<<“sit
Check the “words” that pass here, shorthands like “~site” will already be
expanded here.
In your case you can match on: [<<“site”>>, _Site, <<“flight”>> | _]
But returning true here will indeed allow any user to publish or subscribe to
these topics.
- Marc
> On 30 Nov 2016, at 15:30, heihes
observe_acl_is_allowed(#acl_is_allowed{action=publish,
object=#acl_mqtt{words=[<<"~site">>, <<"flight">>| _Rest]}},
Context) ->
true;
observe_acl_is_allowed(#acl_is_allowed{action=subscribe,
object=#acl_mqtt{words=[<<"~site">>, <<"flight">>| _Rest]}},
Context) ->
true;
as
Yes I can change the context, but not anyone can get this message, only now
the administrator can
суббота, 26 ноября 2016 г., 16:35:59 UTC+9 пользователь Marc Worrell
написал:
>
> Quick reply, as I am away from my keyboard.
>
> MQTT messages are ACL checked by topic. You can check mod_mqtt for a
Quick reply, as I am away from my keyboard.
MQTT messages are ACL checked by topic. You can check mod_mqtt for an example
observer.
If you just want to publish from Erlang, then you can use z_acl:sudo/1 on the
Context. This switches off ACL checks.
- Marc
Sent from my iPhone
> On 26 Nov 2016
how to set the right user to send messages to z_mqtt.
I found that the average user of this site can not send messages
--
---
You received this message because you are subscribed to the Google Groups
"Zotonic developers" group.
To unsubscribe from this group and stop receiving emails from it,
16 matches
Mail list logo