update binder documentation (was: token in the binder-daemon is not enforced)

agreed

I suggest to close this ticket.

If I understand correctly, token is replaced by the cynagora permission check.

It would be nice though to document an example to show how to configure cynagora + binder to enforce a check.

it has to do with token because the token must be validated when loa is checked. I'm going to check that tomorrow. From an other Jira ticket I guess that you compiled the binder without cyna(go)ra support. It explains why the token it not checked.

thanks Jose,

tuto-2 requires authorization, but it has nothing to do with token, right? Its authorization is built in the application logic, i.e., checking password == "please" or not.

Ok, I dont see how the token is handled. I think at least my initial question in the ticket is resolved.

Hi @Teddy Zhai , since Icefish version, the management of token changed. It now relies on a third party to validate the token. In detail, is ask the permisson data for the virtual permission "urn:AGL:token:valid" granted to the current session.

On the other hand, the tutorial number one does not require any autorisation.

That is not the case of the tutorial number 2.

The documentation needs an update.