New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for spontaneous scopes #839

Open
nynymike opened this Issue Jul 1, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@nynymike
Contributor

nynymike commented Jul 1, 2018

There is a requirement for payments to send a transaction id as part of the scope. For example:
pis:4685456787 (where 4685456787 is the id of a certain resource)
or
sign:MmU5OTc1ODU0ODk3MmE4ZTg4MjJhZDQ3ZmExMDE3ZmY3MmYwNmYzZmY2YTAxNjg1MWY0NWMzOTg3MzJiYzUwYw==,RXhhbXBsZSBDb250cmFjdA==

Where the first parameter has a base64url encoded has value, second parameter after, is a label of the document to be signed.

The client should be configured to accept "spontaneous scopes"--as normally any non-registered scope should be rejected.

We also need to add a "spontaneous scope interception script", and map this script in the client configuration.

@nynymike nynymike added the enhancement label Jul 1, 2018

@nynymike nynymike modified the milestones: 3.1.4, 4.0 Jul 1, 2018

@yuriyz

This comment has been minimized.

Contributor

yuriyz commented Nov 19, 2018

It is good idea to design it while we are re-factoring scope handling within this ticket #756.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment