-
Notifications
You must be signed in to change notification settings - Fork 151
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
Comments
It is good idea to design it while we are re-factoring scope handling within this ticket #756. |
I will take over this feature. Re-scheduling it on 4.1 since due date of 4.0 code freeze was yesterday. |
I agree that the requirements are not fully detailed. One point: As I understand from discussion here #1133 (comment) If it used as transaction part in a real-life system the number of registered scoped would increase indefinitely, IMO it is unacceptable. |
Right, in client config we should give ability to specify lifetime of spontaneous scopes (if no lifetime specified then indefinite -> scope will not be cleaned up). |
IMO we should have configurable default TTL instead of indefinite. |
…ty to enable/disable spontaneous scopes for given client. #839
Global oxauth configuration:
Client :
New scope type : |
…ope with specified lifetime. Added spontaneous scopes to cleaner timer. #839
…external spontaneous scope python scripts. #839
…stead of explicitly defining supported types) - in this way when new type is added we are good to go by default. #839
Implemented in master (4.2) |
@yuriyz at which time the "spontaneous scope interception script" is invoked?
|
It is invoked during token request. |
thanks |
I will take over |
I've checked it on latest 4.2. It perfectly works. Changes are saved (LDAP reflects changes as well as UI). |
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.
The text was updated successfully, but these errors were encountered: