You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have read https://github.com/EmbeddedEnterprises/autobahnkreuz/blob/master/auth/feature.md.
From I understood, feature-authorizer-matrix-func is an wamp endpoint. From this endpoint, router can receiver a authorize json-string or other format string.
I think this feature is better than crossbar. crossbar put authorizer matrix into config.json. It results in the problem that client authorizer program modified the config.json. It's a risk and inconvenient in production, because config.json has many other important arguments.
Another thing, authorize model in feature.md is simpler than crossbar. The following examples is used in my current project.
@johannwagner
I'm waiting for Feature Authorization ready(it's TBD now).
I want to know the current implementation and its todo-list about authorization.
Example code is preferable for me, if it's can be provided now.
I have read
https://github.com/EmbeddedEnterprises/autobahnkreuz/blob/master/auth/feature.md
.From I understood,
feature-authorizer-matrix-func
is an wamp endpoint. From this endpoint, router can receiver a authorize json-string or other format string.I think this feature is better than
crossbar
.crossbar
put authorizer matrix intoconfig.json
. It results in the problem that client authorizer program modified theconfig.json
. It's a risk and inconvenient in production, because config.json has many other important arguments.Another thing, authorize model in
feature.md
is simpler thancrossbar
. The following examples is used in my current project.Of course, the current missing features is not core features in authorial.
The text was updated successfully, but these errors were encountered: