Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support OBO #28

Closed
symphony-soufiane opened this issue Oct 4, 2021 · 0 comments · Fixed by #112
Closed

Support OBO #28

symphony-soufiane opened this issue Oct 4, 2021 · 0 comments · Fixed by #112
Labels
good first issue Good for newcomers wip

Comments

@symphony-soufiane
Copy link
Contributor

We would like the workflow to be able to do actions on behalf of a user, maybe by using BDK obo service.
@symphony-soufiane symphony-soufiane added the good first issue Good for newcomers label Oct 4, 2021
@ystxn ystxn added the wip label Jun 3, 2022
symphony-soufiane added a commit to symphony-soufiane/symphony-wdk that referenced this issue Jun 11, 2022
@symphony-soufiane
finos#28: Support OBO
9a6ae4a 
This PR is a first take on OBO support for WDK activities.
An optional property on-behalf-of has been added in SWADL to make an activity call OBO.
In order to avoid making an authentication request for each OBO activity, we introduced a Caffeine cache to cache user obo authentication sessions. The cache is configured in application.yaml file.
For send-message activity, we throw an illegal argument exception when a blast message is done in OBO mode as the api is not obo enabled.
Only sendMessage and addRoomMember activities are supporting obo for now, the other activities will be implemented in a next commit.
@symphony-soufiane symphony-soufiane mentioned this issue Jun 23, 2022
Merged
5 tasks
symphony-soufiane added a commit that referenced this issue Aug 19, 2022
@symphony-soufiane
#28: Support OBO (#112)
98633f8 
* #28: Support OBO
This PR is a first take on OBO support for WDK activities.
An optional property obo has been added in SWADL to make an activity call OBO, when this activity is OBO enabled.
In order to avoid making an authentication request for each OBO activity, we introduced a Caffeine cache to cache user obo authentication sessions. The cache is configured in application.yaml file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers wip
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

#28: Support OBO symphony-soufiane/symphony-wdk
2 participants
@ystxn @symphony-soufiane